This PR addresses issue #1 to hide the private key (which is used for encrypted communication on the Django side).
Changes
I have uncommitted the settings.yaml file and added a settings-example.yaml file.
To run the app again, you have to copy the example file
cp settings-example.yaml settings.yaml
and update the SECRET_KEY entry (ask me about it).
The settings-example.yaml is tracked while settings.yaml is not. So if you want to add new apps, add them in the settings-example.yaml. This behavior is generally also more safe as you do not accidentally migrate new apps; instead you have to explicitly add new changes yourself.
This PR addresses issue #1 to hide the private key (which is used for encrypted communication on the Django side).
Changes
I have uncommitted the
settings.yamlfile and added asettings-example.yamlfile. To run the app again, you have to copy the example fileand update the
SECRET_KEYentry (ask me about it).The
settings-example.yamlis tracked whilesettings.yamlis not. So if you want to add new apps, add them in thesettings-example.yaml. This behavior is generally also more safe as you do not accidentally migrate new apps; instead you have to explicitly add new changes yourself.