Evaluate Nextcloud #67
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Main installation documentation: https://github.com/nextcloud/all-in-one#how-to-use-this
Reverse proxy readme: https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
Mostly interested in determining which components are useful. Also need to determine whether it makes more sense to use an all-in-one solution like this, or split out individual components (like WebDAV, VoIP, Drive, etc.)
assigned to @Jafner
Probably makes more sense to use Linuxserver's image
mentioned in commit
85262dc130
mentioned in commit
d28acbbe58
mentioned in commit
2a5634b9e6
mentioned in commit
08ffc99e37
mentioned in commit
a9185655b2
mentioned in commit
a779a2959f
mentioned in commit
dafe07020c
mentioned in commit
85613cb244
Evaluation: seems pretty sick.
Will close this when we clear out all Nextcloud security & setup warnings:
Nextcloud has been running at https://nextcloud.jafner.net/ for a couple months now. It is hooked up to Keycloak for SSO. The service works great, with a couple long-term issues that must be resolved:
added #75 as child task
added #76 as child task
added #77 as child task
Jafner.net - Nextcloud Admin Overview
Nextcloud - Converting Database Type
Nextcloud - Reverse Proxy
Linuxserver - Docker Nextcloud
Linuxserver - SWAG Setup
Migrate Nextcloud DB to MariaDB
docker-compose down && docker-compose up -d
At this point, we have successfully converted from SQLite to MariaDB. Rechecking the Nextcloud setup warnings, we see we have a new warning:
We
docker exec -it nextcloud_mariadb sh
into the MariaDB container, thencat /config/custom.cnf
and look for the lineinnodb_file_per_table=1
, which is already there because we are using the Linuxserver image for MariaDB.We could verify that this is working by running a mysql command to
SHOW VARIABLES LIKE 'innodb_file_per_table';
, but since this was the default that is not necesary.So next we open a shell in the nextcloud container
docker exec -it -u 1000 nextcloud_nextcloud bash
, navigate into the Nextcloud directorycd /config/www/nextcloud
and set the instance into maintenance modephp occ maintenance:mode --on
.Then, we open a shell back in the MariaDB container
docker exec -it nextcloud_mariadb sh
and open a MySQL sessionmysql -h mariadb -u ncuser -p nextcloud
then enter the password when prompted. Now we can go ahead and change the database character set and collationALTER DATABASE nextcloud CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;
. Quitquit;
.Switching back to the nextcloud container, set the mysql.utf8mb4 variable to true
php occ config:system:set mysql.utf8mb4 --type boolean --value="true"
. Then run a repair on the DBphp occ maintenance:repair
. Disable maintenance modephp occ maintenance:mode --off
.Now we should be able to use Emoji in file names, calendar events, comments, and others. Also that warning should be gone.
Nextcloud Reverse Proxy Header Configuration
https://help.nextcloud.com/t/trusted-reverse-proxy-warning-solved/56761
https://help.nextcloud.com/t/cannot-get-rid-of-the-reverse-proxy-warning/77376/17
After a bunch of trial and error, we got to this state:
Where
172.18.0.31
is the IP of the Traefik container on theweb
docker network on which internet traffic is routed through Traefik to Nextcloud.I've also set Traefik to use this IP explicitly.
added #78 as child task
We have set up a cron job to run
rsync -au /mnt/data/nextcloud/ /mnt/nas/backups/Binary/Nextcloud
daily at midnight.And with that, I believe this issue is closed.