Hardcode initial Nextcloud credentials #900
Merged
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.
The Nextcloud container only respects the some of the configuration environment variables when you hardcode auth parameters. If you let the user manually go through the setup process, configurations settings are set to defaults and the environment variables we set are ignored. Notably whitelisting both the local hostname and the Tor hidden service does not happen when a user manually registers, instead Nextcloud is only accessible over the hostname they accessed the registration form over.
This change hardcodes a default Nextcloud username/password of
umbrel
/moneyprintergobrrr
which triggers the Docker image to run through the automated setup process and respect our environment variables. Added a note explaining users who wish to share files via Nextcloud should update the password before sharing links.We also add a migration step to the update step to fix any existing installs that