beautiful_orca @ beautiful_orca @discuss.tchncs.de Posts 1Comments 9Joined 1 mo. ago
I have my own mollysocket and ntfy, both on tailscale domains with funnel. You can restrict your mollysocket to only your ID.
What makes Sunup different from ntfy? Is it better?
Molly-FOSS is awesome and it now has UnifiedPush support built-in!
Get it with Obtainium
This post explains it, but it is still too complicated for me to figure out: https://doc.dovecot.org/2.4.0/installation/upgrade/2.3-to-2.4.html
I had dovecot running unencrypted IMAP via Tailscale VPN, but with dovecot version 2.4.0 it did not accept my configuration anymore. can you share an easy example?
I was thinking of switching to mailcow so i do not have to configure dovecot myself...
RSSHub (selfhosted)
It has a button to quickly add an entry to your FreshRSS, very useful.
I kind of followed the tutorial, but changed the tailscale configuration to how it is advised by tailscale in their blog about tailscale in docker. It is running fine for me.
compose.yml:
services:
nextcloud-aio-mastercontainer:
image: nextcloud/all-in-one:latest
init: true
restart: always
container_name: nextcloud-aio-mastercontainer
volumes:
- nextcloud_aio_mastercontainer:/mnt/docker-aio-config # do not change
- /var/run/docker.sock:/var/run/docker.sock:ro # do not change
networks:
- nextcloud-aio
ports:
- 8091:8080
environment:
APACHE_PORT: 11000
APACHE_IP_BINDING: 127.0.0.1
SKIP_DOMAIN_VALIDATION: true
nc-caddy:
image: caddy:alpine
container_name: nc-caddy
restart: always
environment:
NC_DOMAIN: nc.tailnet.ts.net
volumes:
- ./caddy/Caddyfile:/etc/caddy/Caddyfile
- ./caddy/caddy_data:/data
- ./caddy/caddy_config:/config
- ./caddy/caddy_certs:/certs
- ./tailscale/tailscale_sock:/var/run/tailscale/:ro
network_mode: service:nc-tailscale
labels:
- com.centurylinklabs.watchtower.enable=true
nc-tailscale:
image: tailscale/tailscale:latest
container_name: nc-tailscale
restart: always
init: true
environment:
- TS_HOSTNAME=nc
- TS_AUTH_KEY=tskey-auth-xxx
- TS_EXTRA_ARGS=--advertise-tags=tag:container
- TS_STATE_DIR=/var/lib/tailscale
volumes:
- ./tailscale/state:/var/lib/tailscale
- ./tailscale/config:/config
- ./tailscale/tailscale_sock:/tmp
devices:
- /dev/net/tun:/dev/net/tun
cap_add:
- net_admin
- sys_module
networks:
- nextcloud-aio
labels:
- com.centurylinklabs.watchtower.enable=true
volumes:
nextcloud_aio_mastercontainer:
name: nextcloud_aio_mastercontainer
networks:
nextcloud-aio:
name: nextcloud-aio
driver: bridge
enable_ipv6: false
Caddyfile:
https://{$NC_DOMAIN}:443 {
reverse_proxy nextcloud-aio-apache:11000
}
The manual istall now seems too cluttered for me, aswell as the caddy webserver configuration. The AIO probably has an more up to date configuration which is vetted by the community.
I will try to configure the AIO version how i like it, but still apply what i have learned connecting tailscale (https://github.com/nextcloud/all-in-one/discussions/5439)
@BakedCatboy@lemmy.ml your example helped clarify the network and service linking, thank you.
So that means i need to link the webserver to the tailscale service
network_mode: service:tailscale
And also add the tailscale to the "proxy" network that is created (like also done in the aio example with
networks: - nextcloud-aio
)