all-in-one VS cloudflared

Link | Demo | Github | License

If you aren't super technical please please go for the all-in-one. The manual docker image is super complicated for an unexperienced user. I'm super well at home in Linux and command lines and I wouldn't even CONSIDER doing it the manual way. The AIO is hard enough, and orders of magnitude simpler. Don't even think about docker compose or all that stuff - go to https://github.com/nextcloud/all-in-one/ and follow that...

Newbie to NC here, hosting at home. Reading through the local-only guide and have a couple of questions, if you don't mind:

I followed https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md

Or this one? https://github.com/nextcloud/all-in-one

I can't figure out the steps to get things running locally. (https://github.com/nextcloud/all-in-one/blob/main/local-instance.md) I'm trying the docker AIO for Windows, and I think I'm on step 2. I've pasted the steps from the link over.. I hope for some guidance here :)

version: "3.8" services: nextcloud: image: nextcloud/all-in-one:latest restart: always container_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed as otherwise AIO will not work correctly volumes: - nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed as otherwise the built-in backup solution will not work - /var/run/docker.sock:/var/run/docker.sock:ro # May be changed on macOS, Windows or docker rootless. See the applicable documentation. If adjusting, don't forget to also set 'WATCHTOWER_DOCKER_SOCKET_PATH'! ports: #- 38983:80 # Can be removed when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md - 38984:8080 #- 38985:8443 # Can be removed when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md environment: # Is needed when using any of the options below - APACHE_PORT=11000 # Is needed when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md - APACHE_IP_BINDING=0.0.0.0 # Should be set when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else) that is running on the same host. See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md - NEXTCLOUD_DATADIR=/storage/nextcloud/data # Allows to set the host directory for Nextcloud's datadir. ⚠️⚠️⚠️ Warning: do not set or adjust this value after the initial Nextcloud installation is done! See https://github.com/nextcloud/all-in-one#how-to-change-the-default-location-of-nextclouds-datadir - WATCHTOWER_DOCKER_SOCKET_PATH=/var/run/docker.sock # Needs to be specified if the docker socket on the host is not located in the default '/var/run/docker.sock'. Otherwise mastercontainer updates will fail. For macos it needs to be '/var/run/docker.sock' - SKIP_DOMAIN_VALIDATION=true volumes: nextcloud_aio_mastercontainer: name: nextcloud_aio_mastercontainer # This line is not allowed to be changed as otherwise the built-in backup solution will not work

services:nextcloud:image: nextcloud/all-in-one:latestrestart: alwayscontainer_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed as otherwise AIO will not work correctlyvolumes:- nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed as otherwise the built-in backup solution will not work- /var/run/docker.sock:/var/run/docker.sock:ro # May be changed on macOS, Windows or docker rootless. See the applicable documentation. If adjusting, don't forget to also set 'WATCHTOWER_DOCKER_SOCKET_PATH'!ports:- 81:81 # Can be removed when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md- 8080:8080- 8443:8443 # Can be removed when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.mdenvironment: # Is needed when using any of the options below# - AIO_DISABLE_BACKUP_SECTION=false # Setting this to true allows to hide the backup section in the AIO interface. See https://github.com/nextcloud/all-in-one#how-to-disable-the-backup-section- APACHE_PORT=11000 # Is needed when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md- APACHE_IP_BINDING=0.0.0.0 # Should be set when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else) that is running on the same host. See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md# - BORG_RETENTION_POLICY=--keep-within=7d --keep-weekly=4 --keep-monthly=6 # Allows to adjust borgs retention policy. See https://github.com/nextcloud/all-in-one#how-to-adjust-borgs-retention-policy# - COLLABORA_SECCOMP_DISABLED=false # Setting this to true allows to disable Collabora's Seccomp feature. See https://github.com/nextcloud/all-in-one#how-to-disable-collaboras-seccomp-feature# - NEXTCLOUD_DATADIR=/mnt/ncdata # Allows to set the host directory for Nextcloud's datadir. ⚠️⚠️⚠️ Warning: do not set or adjust this value after the initial Nextcloud installation is done! See https://github.com/nextcloud/all-in-one#how-to-change-the-default-location-of-nextclouds-datadir# - NEXTCLOUD_MOUNT=/mnt/ # Allows the Nextcloud container to access the chosen directory on the host. See https://github.com/nextcloud/all-in-one#how-to-allow-the-nextcloud-container-to-access-directories-on-the-host- NEXTCLOUD_UPLOAD_LIMIT=500G # Can be adjusted if you need more. See https://github.com/nextcloud/all-in-one#how-to-adjust-the-upload-limit-for-nextcloud- NEXTCLOUD_MAX_TIME=10800 # Can be adjusted if you need more. See https://github.com/nextcloud/all-in-one#how-to-adjust-the-max-execution-time-for-nextcloud- NEXTCLOUD_MEMORY_LIMIT=1536M # Can be adjusted if you need more. See https://github.com/nextcloud/all-in-one#how-to-adjust-the-php-memory-limit-for-nextcloud# - NEXTCLOUD_TRUSTED_CACERTS_DIR=/path/to/my/cacerts # CA certificates in this directory will be trusted by the OS of the nexcloud container (Useful e.g. for LDAPS) See See https://github.com/nextcloud/all-in-one#how-to-trust-user-defined-certification-authorities-ca# - NEXTCLOUD_STARTUP_APPS=deck twofactor_totp tasks calendar contacts notes # Allows to modify the Nextcloud apps that are installed on starting AIO the first time. See https://github.com/nextcloud/all-in-one#how-to-change-the-nextcloud-apps-that-are-installed-on-the-first-startup# - NEXTCLOUD_ADDITIONAL_APKS=imagemagick # This allows to add additional packages to the Nextcloud container permanently. Default is imagemagick but can be overwritten by modifying this value. See https://github.com/nextcloud/all-in-one#how-to-add-os-packages-permanently-to-the-nextcloud-container# - NEXTCLOUD_ADDITIONAL_PHP_EXTENSIONS=imagick # This allows to add additional php extensions to the Nextcloud container permanently. Default is imagick but can be overwritten by modifying this value. See https://github.com/nextcloud/all-in-one#how-to-add-php-extensions-permanently-to-the-nextcloud-container# - NEXTCLOUD_ENABLE_DRI_DEVICE=true # This allows to enable the /dev/dri device in the Nextcloud container. ⚠️⚠️⚠️ Warning: this only works if the '/dev/dri' device is present on the host! If it should not exist on your host, don't set this to true as otherwise the Nextcloud container will fail to start! See https://github.com/nextcloud/all-in-one#how-to-enable-hardware-transcoding-for-nextcloud# - TALK_PORT=3478 # This allows to adjust the port that the talk container is using. See https://github.com/nextcloud/all-in-one#how-to-adjust-the-talk-port# - WATCHTOWER_DOCKER_SOCKET_PATH=/var/run/docker.sock # Needs to be specified if the docker socket on the host is not located in the default '/var/run/docker.sock'. Otherwise mastercontainer updates will fail. For macos it needs to be '/var/run/docker.sock'- SKIP_DOMAIN_VALIDATION=true# networks: # Is needed when you want to create the nextcloud-aio network with ipv6-support using this file, see the network config at the bottom of the file# - nextcloud-aio # Is needed when you want to create the nextcloud-aio network with ipv6-support using this file, see the network config at the bottom of the file# # Optional: Caddy reverse proxy. See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md# # You can find further examples here: https://github.com/nextcloud/all-in-one/discussions/588# caddy:# image: caddy:alpine# restart: always# container_name: caddy# volumes:# - ./Caddyfile:/etc/caddy/Caddyfile# - ./certs:/certs# - ./config:/config# - ./data:/data# - ./sites:/srv# network_mode: "host"volumes:nextcloud_aio_mastercontainer:name: nextcloud_aio_mastercontainer # This line is not allowed to be changed as otherwise the built-in backup solution will not work# # Optional: If you need ipv6, follow step 1 and 2 of https://github.com/nextcloud/all-in-one/blob/main/docker-ipv6-support.md first and then uncomment the below config in order to activate ipv6 for the internal nextcloud-aio network.# # Please make sure to uncomment also the networking lines of the mastercontainer above in order to actually create the network with docker-compose# networks:# nextcloud-aio:# name: nextcloud-aio # This line is not allowed to be changed as otherwise the created network will not be used by the other containers of AIO# driver: bridge# enable_ipv6: true# ipam:# driver: default# config:# - subnet: fd12:3456:789a:2::/64 # IPv6 subnet to use

It is basically all images and services pre-configured to host a single Nextcloud instance. Check this page https://github.com/nextcloud/all-in-one

Cloudflare Tunnel - Excellent free option. Nicely integrates tunneling with the rest of Cloudflare's products, which include DNS and auto HTTPS. Client source code is Apache 2.0 licensed and written in Golang.

I run a RaspberryPi 3 with FreeBSD 13 booting off an SD card and a USB SSD for storage [1]. Coincidentally today (1/7/2024) is its one year anniversary.

It runs a jail with my single user GotoSocial ActivityPub server [2] reasonably well with cloudflared [3] handling incoming traffic and acting as CDN to take some of the load. Originally it was only using an SD card, but there was too much IO contention so a USB-SSD adapter is used to offload the IO.

I choose FreeBSD over Linux since I have other Rpis with Linux already and wanted more experience with *BSD, jails, and ZFS. Unfortunately ZFS wasn't the best choice on an Rpi since it's more cpu intensive and switched back to UFS.

Overall it's been solid, multiple GTS updates and have it on my list to update to FreedBSD 14 but not really in a rush.

1. https://social.ecliptik.com/@micheal/statuses/01GP860MYM2CGH...

2. https://gotosocial.org/

3. https://github.com/cloudflare/cloudflared

# Install apt dependencies !apt install dotnet-sdk-7.0 git # Install Clouldflared (not on apt) !wget https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64.deb !dpkg -i cloudflared-linux-amd64.deb # Download StableSwarmUI !git clone https://github.com/Stability-AI/StableSwarmUI # Download ComfyUI backend %cd /content/StableSwarmUI !mkdir /content/StableSwarmUI/dlbackend %cd /content/StableSwarmUI/dlbackend !git clone https://github.com/comfyanonymous/ComfyUI %cd /content/StableSwarmUI/dlbackend/ComfyUI # Setup ComfyUI !pip install -r requirements.txt

curl -L --output cloudflared.deb https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64.deb && sudo dpkg -i cloudflared.deb && sudo systemctl restart cloudflared

Something like cloudflared would be awesome. https://github.com/cloudflare/cloudflared

if you're on windows, you can install it with the exe: https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-windows-amd64.exe (or https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-windows-386.exe if your using 32bit windows.)

So, the "more than one" issue is kind of discussed HERE and HERE but for sure, for whatever reason, this caused me sleepless nights.

%cd /content/naifu !pip install virtualenv && bash ./setup.sh !curl -Ls https://github.com/ekzhang/bore/releases/download/v0.4.0/bore-v0.4.0-x86_64-unknown-linux-musl.tar.gz | tar zx -C /usr/bin !curl -Lo /usr/bin/cloudflared https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64 && chmod +x /usr/bin/cloudflared !/content/naifu/venv/bin/python -m pip install -qq pytorch_lightning==1.7.7

Anyway, here is the Github link for Cloudflared (aka Cloudflare Tunnel client) which should allow you to remotely tunnel into your Synology server instead of using the HTTP-based reverse proxying method: https://github.com/cloudflare/cloudflared

As an alternative to traditional ingress, you can use cloudflared to expose web apps on Cloudflare via encrypted tunnels: https://github.com/cloudflare/cloudflared