Flarum install wizard not listing all the required Nginx directory permissions?

ron_jeremy

I just tried installing Flarum beta 5 on Nginx for the first time. When I accessed the IP of my site to continue with the install gui, Flarum prompted to modify the following directory permissions:

The /usr/share/nginx/html directory is not writable.
Please chmod this directory to 0775.

The /usr/share/nginx/html/assets directory is not writable.
Please chmod this directory and its contents to 0775.

The /usr/share/nginx/html/storage directory is not writable.
Please chmod this directory and its contents to 0775.

So, I ran the following commands:

chmod 775 /usr/share/nginx/html

chmod -R 775 /usr/share/nginx/html/assets

chmod -R 775 /usr/share/nginx/html/storage

However, the directory issues still persisted. Did I do something wrong?

The only way for me to get to the next step was to add the following commands even though the Flarum installer did not suggest to do so:

chgrp www-data /usr/share/nginx/html

chgrp -R www-data /usr/share/nginx/html/assets

chgrp -R www-data /usr/share/nginx/html/storage

Thoughts? Should the installer have prompted to run the chgrp commands, or is that something that is simply expected?

Davis

ron_jeremy The files naturally should be owned by the web server group. Perhaps it would be a good idea to have the installer suggest that, but for experienced users, it's a given (but so is chmod 775)

sijad

ron_jeremy there is an open issue here https://github.com/flarum/core/issues/890

ron_jeremy

Davis The files naturally should be owned by the web server group

That might be true, but I wouldn't know. I started with the automated LEMP install on DigitalOcean. I might be wrong, but I think the Apache install suggests all commands (chmod and chgrp).

ron_jeremy

sijad That is great!

Franz

It's hard to figure out exact instructions here, because configurations are often so different. We want these directories to be writable, but there are various ways to do that, and some of them don't work in some environments, apparently.

That issue exists because we want to get smarter about making suggestions for commands to run. If you know how we can get there, please let us know. ?