Document storage directory permissions - #28
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
馃挕 Tip: Enable Workflows to automatically generate PRs for you. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
馃挕 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f4573ac266
鈩癸笍 About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 馃憤.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Ensure the user running your web server can write to Cachet's `storage` directory. Cachet uses this | ||
| directory for logs, cached files, sessions, and other runtime data. |
There was a problem hiding this comment.
On deployments where nginx and PHP-FPM run under different accounts, granting access to the web-server user does not let the PHP process write Cachet's runtime data; the scheduler and dedicated queue worker documented below can likewise run as separate users. Specify that the PHP-FPM/application, scheduler, and queue-worker users must all have appropriate access to storage, otherwise these supported configurations can still fail with permission errors.
Useful? React with 馃憤聽/ 馃憥.
1 participant
Summary
storagedirectoryWhy
Without this requirement, a new installation can fail at runtime when Cachet needs to write application data.
Closes #13
Validation
git diff --checkmintlifycommand is not installed locally.