Document how to use `NC_*` environment variables with Nextcloud Server via the image
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 7.4k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
- via
docker run/ command line - via
docker compose/ Compose File
Should significantly cut down on many requests to add additional configuration variables to the image.
E.g.
Optionally, most configuration parameters of Nextcloud otherwise normally specified in thr
config.phpcan be specified (or overriden) using Nextcloud's built-in in - but undocumented and somewhat discouraged officially - support for injectingNC_*config values via the environment. Note this last approach should not be used for any parameters supported by the image already. It's also not well documented or supported upstream.
Refs:
- nextcloud/server#3966
- nextcloud/documentation#426
- nextcloud/documentation#9143
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked Nextcloud server and documentation references, then inspect this repository's existing Docker usage documentation. Document NC_* configuration through both docker run and Docker Compose, including the stated caveats and exclusions; done means users can follow either workflow without requesting separate image variables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- Half a day
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100