Behaviour and protocol

Code of conduct Code reviews Consulting 101 Feedback Good meetings practices How to facilitate team meetings Inclusive language Values

Career

360 review Continuing education policy Engineering manager career ladder Roles Software engineer progression framework Technical skills sheet

Employee manual

Abtion's pomodoro Employee benefits Internal days & community Intro Parental leave policy Safety and security Schedule, time tracking & calendar Sickness & unplanned absence Travelling Vacation & planned time off Work from anywhere policy

Project management

Technical setup when starting a new project Client discontinuing hosting or sla Converting projects from development to maintenance mode Estimating Go live checklist Handoffs Invoicing guidelines Procedure for traffic Sla

Setup

Audio setup Database backup setup Gpg signing

Technical practices

Commit messages Kick off meeting Pair programming Testing strategy Workflow

Templates

Readme.standard

Tools and services

Access and permissions Ai tools Purchasing licenses and memberships Sharing sensitive information Stack and services Wordpress
=

Setup

Database backup setup

An s3 bucket (abtion-backups) has been created for securely storing encrypted database copies for clients with SLA.

Scalingo

TODO: This section needs to be written. Document how to set up automated database backups for Scalingo-hosted projects, including where credentials are stored and how to verify backups are running.

Heroku

The AWS credentials for the user with write access to the bucket is in 1Password internal infrastructure vault (AWS backups - s3-uploader).

For detailed instructions, see: https://github.com/abtion/heroku-db-backup-s3

Use abtion-backups as bucket name. Use client name for gpg real name. Use client-name@abtion.com for gpg email address.

The gpg private keys should be moved to the Technical Red Tape vault or ask for it to be moved in #access-and-permissions slack channel.

✏️ Edit this page on GitHub