Timeline for What are the correct file permission settings for magento 2.2 on a single-user production environment?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2018 at 8:10 | vote | accept | user125661 | ||
| Aug 9, 2018 at 8:07 | history | edited | ByteCreation | CC BY-SA 4.0 | deleted 1136 characters in body |
| Aug 9, 2018 at 7:52 | comment | added | user125661 | Thanks! Maybe you could put that in a separate answer so I can accept that? | |
| Aug 9, 2018 at 7:26 | comment | added | ByteCreation | Here's an explanation of what each folder does in var: devdocs.magento.com/guides/v2.2/howdoi/php/php_clear-dirs.html . It makes sense that view_preprocessed made read only after the files have been generated, also makes sense that the generated folder is write only after its generated, but some things can't be read only in var. Looks like a devdocs mistake with the command not doing what the best practice describes above it. | |
| Aug 9, 2018 at 7:21 | comment | added | ByteCreation | Var cannot be read only for the user running hosting software. Example: log writing. Parts of it maybe, and if logs are managed by a different system maybe, but not out of the box. | |
| Aug 9, 2018 at 7:20 | comment | added | ByteCreation | I see what you mean. The devdocs say that for production mode for single user, that var/view_preprocessed should not have write permissions, but the command they offer removes write access to var. | |
| Aug 9, 2018 at 7:05 | comment | added | user125661 | I am on a single-user environment (edited question to add that information). Both owner and group of all files are set to this user. My question is, why does the documentation state to make var read-only, while Magento does seem to need to write to it? | |
| Aug 9, 2018 at 6:47 | history | answered | ByteCreation | CC BY-SA 4.0 |