In Prerequisites I find the line you may want to create a dedicated user specifically for running Pixelfed. You can than create the user 'pixelfed'. Also the PHP-FPM configuration works with the pixelfed user.
Later into the installation documentation is not always clear that you should use this user. Example: composer install --no-ansi --no-interaction --optimize-autoloader will give problems when running as root, so this should be (in the pixelfed directory as the pixelfed user): sudo -u pixelfed composer install --no-ansi --no-interaction --optimize-autoloader. Probably there are more examples.
The solution would be to always assume users are running it as the pixelfed user and never as http or www-data, or the other way around (e.g. as www-data on Debian/Ubuntu).
In Prerequisites I find the line
you may want to create a dedicated user specifically for running Pixelfed. You can than create the user 'pixelfed'. Also the PHP-FPM configuration works with the pixelfed user.Later into the installation documentation is not always clear that you should use this user. Example:
composer install --no-ansi --no-interaction --optimize-autoloaderwill give problems when running as root, so this should be (in the pixelfed directory as the pixelfed user):sudo -u pixelfed composer install --no-ansi --no-interaction --optimize-autoloader. Probably there are more examples.The solution would be to always assume users are running it as the pixelfed user and never as http or www-data, or the other way around (e.g. as www-data on Debian/Ubuntu).