Skip to content
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.

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

Q: Updating System Installed with this Script #75

Closed
LinuksGuru opened this issue Nov 14, 2020 · 2 comments
Closed

Q: Updating System Installed with this Script #75

LinuksGuru opened this issue Nov 14, 2020 · 2 comments

Comments

@LinuksGuru
Copy link

Hi !

I have NextCloud (with self-signed certificate) running as Ubuntu18LTS KVM appliance running under oVirt. Currently planning to migrate to Debian 10 Docker installation made with this great script (also with self-signed certificate + Collabora). Before I would like to understand 2 things:

  1. What is proper upgrade method? Pulling docker image, built-in NextCloud upgrade tools or simply re-run this script?
  2. I have trusted domains defined as 3 IP addresses - 1 internal LAN + 2 external, in current system defined with trusted_domains variable. Are trusted domains should be defined somewhere in playbook or later with manual edit of config file, in order to be preserved during upgrade process?

Thanks in advance.

@ReinerNippes
Copy link
Owner

Hi.

  1. built-in NextCloud upgrade <- doesn't work with docker images to my understanding.
    if you didn't change anything all images will autoupdate.

    com.centurylinklabs.watchtower.enable: "true"

    this label tell the watchtower container to check once per day for new images and pull them automatically.
    worked for me fine. so far.
    if you don't want this you can define the image version in this file:
    docker_nextcloud_image: fpm-alpine

    e.g.: 20-fpm-alpine to stay on nextcloud 20.
    note: don't change the postgres and fulltextsearch images to latest. postgres doesn't auto upgrade from major numbers and the fulltextsearch images my not be compatible.

  2. you want to access nextcloud through three domains? example.com, example.org, example.tld
    yon can add trusted domains here:

    - "trusted_domains 0 --value={{ nextcloud_server_fqdn }}"

    but more important tell traefik to route more then one domain here:
    traefik.http.routers.nginx-http.rule: "Host(`{{ nextcloud_server_fqdn }}`)"

    and here
    traefik.http.routers.nginx.rule: "Host(`{{ nextcloud_server_fqdn }}`)"

    the statement has to look like:

traefik.http.routers.nginx.rule: "Host(`example.com`) || Host(`example.org`) || Host(`example.tld`)

https://doc.traefik.io/traefik/routing/routers/#rule
this applys to the nginx/fpm-php config.
you have to define one domain in the inventory still because the variable nextcloud_server_fqdn is used for portainer and adminer.

@LinuksGuru
Copy link
Author

Fixed with 1 trusted domain and IP switching with router/DNS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants