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
The opencloud binary itself uses https://localhost:9200 which works ok for local development. However, as soon as subdomains come into play any you start to use containers to contain some of the riskier services localhost no longer routes to the correct container. While the virus scanner does not need to fetch bytes the thumbnailer and the office suite need to make requests between each other. Without routable subdomains this does not work ...
We could teach traefik to route e.g. collabora.localhost to collabora, but collabora itself will then try to make a request to opencloud.localhost ... which won't work.
Personally, I would prefer to align all occurrences in the docker compose file, in the documentation, in the swagger api docs, and in a future helm chart to {service}.example.test. That best mimics an actual deployment. Furthermore, openid connect requires https which makes setting up a smooth dev environment a little painful because you need to use something like mkcert to get rid of self signed certificate errors.
I would be happy to lower the barrier of entry ... so a PR that changes all defaults in the docker compose full example with a working localhost tld is welcome. I doubt it works, prove me wrong ;-)
Is your feature request related to a problem? Please describe.
Do not need to edit /etc/hosts for testing
Describe the solution you'd like
Use a wellknown topleveldomain, which is solved to current machine
The text was updated successfully, but these errors were encountered: