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
We've multiple times seen people who claim to not want to use docker compose in production and still want to use TLS for their compose deployments. this ticket is to track that request further, and for linking any in-development PRs on the topic.
My view is that any connections to localhost do not need to be encrypted, and if docker compose is used on a server and you're connected to that server, I would advise using reverse proxies such as nginx on that server. Is there a use case that falls outside of what I laid out?
such as a user in non-production that wants compose to install camunda on a server and specifically cannot use a reverse proxy? or is configuring a reverse proxy the same level of complexity as configuring spring for TLS? If you have ideas, let me know here.
We've multiple times seen people who claim to not want to use docker compose in production and still want to use TLS for their compose deployments. this ticket is to track that request further, and for linking any in-development PRs on the topic.
related to: #287
The text was updated successfully, but these errors were encountered: