The process of setting up the development environment is currently very convoluted. This is an open-ended issue we could address in a few ways:
Improved documentation The documentation feels sort of disorganized and complicated—especially to a new developer. A more centralized set of docs could improve this. Perhaps we could use GitHub's wiki functionality.
Quick-start script We could create a "quick start" script for getting a simple development environment up and running. It would automatically build the Docker image, create a container, generate system and machine config files, install and enable SSH, generate an SSH key, generate an SSL certificate, and create a user account for the web dashboard. This would allow the developer to easily start working and testing backups on localhost. All that he/she would have to do is enter an email and password for testing the backup summary email.
The process of setting up the development environment is currently very convoluted. This is an open-ended issue we could address in a few ways:
The documentation feels sort of disorganized and complicated—especially to a new developer. A more centralized set of docs could improve this. Perhaps we could use GitHub's wiki functionality.
We could create a "quick start" script for getting a simple development environment up and running. It would automatically build the Docker image, create a container, generate system and machine config files, install and enable SSH, generate an SSH key, generate an SSL certificate, and create a user account for the web dashboard. This would allow the developer to easily start working and testing backups on
localhost
. All that he/she would have to do is enter an email and password for testing the backup summary email.