arno/etesync-server
1
0
Fork 0
mirror of https://github.com/etesync/server synced 2024-11-22 16:58:08 +00:00
Code Issues Releases Wiki Activity

Make it clear in README that backing up secret.txt is ok

Browse Source
This commit is contained in:
Mohammed Anas 2021-07-29 17:10:56 +00:00 committed by Tom Hacohen
parent d4de717cf7
commit d11504093c
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -109,9 +109,10 @@ The default configuration creates a file “`secret.txt`” in the project’s
base directory, which is used as the value of the Django `SECRET_KEY` base directory, which is used as the value of the Django `SECRET_KEY`
setting. You can revoke this key by deleting the `secret.txt` file and the setting. You can revoke this key by deleting the `secret.txt` file and the
next time the app is run, a new one will be generated. Make sure you keep next time the app is run, a new one will be generated. Make sure you keep
the `secret.txt` file secret (don’t accidentally commit it to version the `secret.txt` file secret (e.g. don’t accidentally commit it to version
control, exclude it from your backups, etc.). If you want to change to a control). However, backing it up is okay, and it makes it easier to restore
more secure system for storing secrets, edit `etesync_server/settings.py` the database to a new EteSync server, but it's not essential. If you want to
change to a more secure system for storing secrets, edit `etesync_server/settings.py`
and implement your own method for setting `SECRET_KEY` (remove the line and implement your own method for setting `SECRET_KEY` (remove the line
where it uses the `get_secret_from_file` function). Read the Django docs where it uses the `get_secret_from_file` function). Read the Django docs
for more information about the `SECRET_KEY` and its uses. for more information about the `SECRET_KEY` and its uses.