Skip to content

docs(readme): clarify CMD override behavior for init/update logic #2563

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
joshtrichards wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs(readme): clarify CMD override behavior for init/update logic #2563

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -273,13 +273,15 @@ One or more trusted domains can be set through environment variable, too. They w

### Image specific

The install and update script is only triggered when a default command is used (`apache-foreground` or `php-fpm`). If you use a custom command you have to enable the install / update with
The image’s entrypoint uses the container’s startup command (the image `CMD`, or your Compose `command:`) to decide whether to run its install/update logic. If you override the default `CMD` with a custom one (for example `supervisord`), the entrypoint no longer sees the expected `apache-foreground` / `php-fpm` startup command and therefore will not automatically run the install/update handling unless explicitly enabled.

To force install/update handling with a custom `CMD` / `command:`, set the following to `1`:

- `NEXTCLOUD_UPDATE` (default: `0`)

You might want to make sure the htaccess is up to date after each container update. Especially on multiple swarm nodes as any discrepancy will make your server unusable.
You may also want to ensure `.htaccess` is refreshed after container startup, especially in multi-node/swarm deployments where inconsistencies can make the instance unusable. Setting the following variable will run `occ maintenance:update:htaccess` after initialization:

- `NEXTCLOUD_INIT_HTACCESS` (not set by default) Set it to true to enable run `occ maintenance:update:htaccess` after container initialization.
- `NEXTCLOUD_INIT_HTACCESS` (not set by default)

### Redis Memory Caching

Expand Down
Loading