trent_larson/py-push-server
4
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

add more help to the permissions troubleshooting

Browse Source
This commit is contained in:
Trent Larson
2023-12-17 18:11:27 -07:00
parent 1edeb89144
commit cc001692eb
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -283,4 +283,10 @@ Troubleshooting
SQLALCHEMY_DATABASE_URI with `sqlite:////...` with the full path to the data/webpush.db file. SQLALCHEMY_DATABASE_URI with `sqlite:////...` with the full path to the data/webpush.db file.
(Why does the relative path of `sqlite:///...` not work for a relative path?) (Why does the relative path of `sqlite:///...` not work for a relative path?)
* Another potential problem with "unable to open database file" is the permissions on the directory or file with the DB, as set on the local volume that matches the docker `/app/instance/data` directory. Note that the user id in the Dockerfile is set to 1000; the `id` command will tell you the uid for your user, which should match. * Another potential problem with "unable to open database file" is the
permissions on the directory or file with the DB, as set on the local volume
that matches the docker `/app/instance/data` directory. Note that the user id
in the Dockerfile is set to 1000; the `id` command will tell you the uid for
your user, which should match. Then, user with uid 1000 should have write
permissions to both the file and the directory, and have execute permissions
to the whole path to that directory.