Closed andrey-genpracc closed 1 month ago
You probably want a maximum of one syncthing in a shared environment so I should add an environment switch to allow user choice for startup services. I can do that tomorrow.
Really my primary use case has always been running in a single container cloud setup but I'm actively thinking about how to provide the same user experience without over-bundling - it'll take a while to achieve that but it'll be beneficial for local users I hope
Now supports passing SUPERVISOR_NO_AUTOSTART=syncthing
A unique Auth cookie will be set for each container to prevent collisions in the same use case
When i started 3 containers with different ports and one workspace i am having stucking state of loading in all containers. Apparelently problem in syncthing . Should i make different configs for syncthing or smth else ?
logs :
my docker-compose :