Closed maicol07 closed 5 years ago
You are apparently executing Weblate under different users - the management commands are executed under maicol07
while the web runs as www-data
. This is actually described in the documentation link you were given.
What do you recommend to do? Adjusting file ownership to www-data:www-data
and executing managements command under this user?
There's a bug in the sample celery-worker.service file - it Uses PermissionsStartOnly - that in turn means that it the permissions are not dropped when running reload, thus causing the celery process to run as root. Better solution is to use corresponding runtimeDir and Logsdir directives.
RuntimeDirectory=celery
RuntimeDirectoryPreserve=restart
LogsDirectory=celery
that not only makes the ExecPre commands to setup those dirs superfluous, but also gets rid of the PermissionsStartOnly, so proper user/group is used even on reload.
@nijel how can @cloph suggestion be implemented?
@cloph Thanks for pointing out, but that's not the issue @maicol07 has hit as his files were not root
owned. I've changed this in c614dd1959.
Describe the bug Weblate creates non-writable files. Weblate works as normal but when I execute
weblate check --default
this is one line of the output (same error message for a lot of files):?: (weblate.E002) Path /var/www/html/weblate/data/avatar-cache/36a16278f9bf62f1cb59ad59290b8f0b.djcache is not writable, check your DATA_DIR settings.
To Reproduce Steps to reproduce the behavior:
Expected behavior Weblate creates writable files
Server configuration and status Output of
weblate list_versions
:Output of
weblate check --deploy
:Additional context Weblate is installed on Linux Mint 19.3 (Ubuntu 18.04 LTS) using venv. Files created by weblate are owned by
www-data:www-data
with0600
permissions, while other files are owned bymaicol07:maicol07
(me) with0777
permissions.