I was just looking to see what others do in regards to backing up the configuration (env) directory, and if you how you go about reusing it for other systems such as test and dev that could be on local users systems.
I guess my ideal solution would to put the env directory into git and track changes that way, but there are passwords placed in the files, that I would rather not commit if I didn’t need to, and having the passwords makes it a little more difficult switch between environments. Or are there certain files I should ignore completely and just have part of the steps to setting up be run
tutor config save ? I know running tutor with a new version does wipe out some of these files (which makes sense), but not every file has a “patch” option such as the requirements.txt and Dockerfile that I had to change when migrating from native to tutor (juniper).
I guess I would like to be able to give our developers an environment as close to production as possible, without actual user data. For example, be able to have the courses and theme available for them to do development with on their laptop / desktop and be able to submit Pull Requests to the main repository to have those changes be brought into the main repo for further testing and deployment.
Thanks for any insight you have!