Document required write permissions for modules/ and public/ext/ - #31
Open
mickaelburggraeve9-wq wants to merge 1 commit into
Open
Conversation
The addon/module system (Admin → Addons) requires the webserver user to have write access to these two directories, but they aren't listed in the Permissions Errors section alongside bootstrap/, storage/logs/, etc. Installing an addon fails with "Failed to place addon: X" when this isn't set up, which isn't obvious from the current docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Permissions Errors section of the v8.x installation docs lists the directories that need to be writable by the webserver user (
bootstrap,bootstrap/cache,storage/logs,storage/framework/{cache,session,views}), but doesn't mentionmodules/andpublic/ext/, which are used by the addon/module system (Admin → Addons,App\Addons\AddonRegistry).Without write access to these two directories, installing an addon fails with
Failed to place addon: <name>— a silentFile::moveDirectory()failure. Since these directories aren't part of the initial installer's requirements check (addons are installed after setup, on an already-running site), this is easy to miss and not obvious from the current docs.Confirmed by tracing
AddonRegistry::install()/update()in the phpvms/phpvms source, and reproducing the exact failure on a manually-deployed (non-Docker) install wheremodules/andpublic/ext/weren't owned/grouped for the webserver user. Note this doesn't affect the official Docker deployment path, sinceDockerfile.prodruns everything aswww-datafrom the start.Change
Adds a short note + the two missing directories to the existing bullet list, same style as the surrounding content.