Scope filesystem permissions and drop sudo from the cache clear - #31
Merged
Merged
Conversation
Signed-off-by: arhimede <julian@dotkernel.com>
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
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.
Four code blocks made
dataandlogworld-writable, and one told the reader to clear the config cache as root.chmod -R 777ondataandlogis replaced with group ownership for the web-server user and775. These are directories the web server writes into, and they hold the Twig and config caches, which are executable PHP — world-writable is a bad default to publish, and the pages offered no alternative and no scoping to local development.777is now mentioned once, in the FAQ, labelled as a throwaway-VM last resort.apacheon AlmaLinux and RHEL derivatives, since the page recommends AlmaLinux and the example sayswww-data.sudo php ./bin/clear-config-cache.phpbecomescomposer clear-config-cache, with nosudo. Running it as root leaves the regenerateddata/cache/config-cache.phpowned by root and the application cannot rewrite it — which reproduces the exact permission errors the FAQ page exists to fix.