-
Notifications
You must be signed in to change notification settings - Fork 100
Add the proxy to the local docker compose file #68
Conversation
This allows users to start the whole Unleash system (including the proxy) with a single command.
Also: use `UNLEASH_PROXY_CLIENT_KEYS` instead of the deprecated `UNLEASH_PROXY_SECRETS`.
# Disable SSL for database connections. @chriswk: why do we do this? | ||
DATABASE_SSL: "false" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chriswk Do you want to explain to me again what this does and why it's necessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because otherwise we'd have to configure an SSL certificate for the postgres container, and get the unleash image to trust a custom SSL certificate. Instead we run an unencrypted connection against postgres in this demo setup
# trust incoming connections blindly (DON'T DO THIS IN PRODUCTION!) | ||
POSTGRES_HOST_AUTH_METHOD: "trust" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What exactly does this do and why do we need it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It allows us to not configure username/passwords for any user. See https://hub.docker.com/_/postgres for further documentation
This PR adds the Proxy to the list of services that the docker compose file spins up. This makes it easier for users to start the whole Unleash system.
To achieve this, we start the Unleash server with a default client token.
This PR also adds some explanatory comments to the docker compose file to let the user know what the various environment variables do.