You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Hey, you only need to point traefik to port 80 of seafile-caddy, it'll do the rest."
That sounds very simple; currently in my traefik.yml file I have
entrypoints:
web:
address ":80"
I have a number of containerized services currently working with traefik (adminer, portainer, kanboard, and before I wrecked it: nextcloud). Will changing that port to seafile caddy ruin those containers? I'd be happy to change from traefik to something else for managing certificates, but it took me long enough (and a lot of help!) to get traefik working. And I don't have a lot of time to learn a new system: I'm looking for something plug-and-play-ish. Anyway, any help on how to manage seafile and caddy with traefik would be very helpful! Many thanks.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
According to an answer nearly two years ago:
"Hey, you only need to point traefik to port 80 of seafile-caddy, it'll do the rest."
That sounds very simple; currently in my traefik.yml file I have
I have a number of containerized services currently working with traefik (adminer, portainer, kanboard, and before I wrecked it: nextcloud). Will changing that port to seafile caddy ruin those containers? I'd be happy to change from traefik to something else for managing certificates, but it took me long enough (and a lot of help!) to get traefik working. And I don't have a lot of time to learn a new system: I'm looking for something plug-and-play-ish. Anyway, any help on how to manage seafile and caddy with traefik would be very helpful! Many thanks.
Beta Was this translation helpful? Give feedback.
All reactions