I've been able to remove the ports declarations yes - since I already have kanboard on a different port vikunja can use 80/443 (but not specifying a port for multiple services which run on 80 or 443 results in an error when running 'docker-compose up': "port is already allocated").
Still haven't been able to get things functioning though.
Might bring down my whole stack and try with some of the example compose files alone. About ready to throw in the towel though. I don't think it's vikunja's fault so much as my inexperience with docker and traefik.
I experimented with only starting the backend - no response with curl until I added ports "3456:3456", which makes sense.
Then get a response on:
curl http://your-vikunja-url.com:3456/api/v1/info
of
{"version":"0.10+24-88bf8f3df0","frontend_url":"","motd":"","link_sharing_enabled":true,"max_file_size":"20MB","registration_enabled":true,"available_migrators":null,"task_attachments_enabled":true}
Obviously curl wasn't going to get a response without the backend allowing connection to the outside world? Does the frontend need that too though? I'd assumed the back and front end being on the same 'backend' docker network would be enough...
Still can't register or login once the frontend is started. I also don't have fully functioning https yet.
Attaching a sanitized docker-compose.yml and the two jinja2 templates I have ansible copy into place for traefik config - mostly just vars for domain name etc. I hope their clear enough.
If I include the port number I defined in my docker-compose:
curl http://your-vikunja-url.com:10110/api/v1/info
I get "We're sorry but Vikunja doesn't work properly without JavaScript enabled" etc.
Which doesn't seem llike 'info'? Visiting that url in the browser gives a TypeError "navigator.serviceWorker is undefined". Actually I get that error on the login and register pages too...
I'm using traefik v2, so not exactly the the example from the docs, no. A conversion of it, also not quite the same as the one given on reddit
I'm adding it to a stack with traefik, portainer and kanboard already present.