Closed jordanparker6 closed 2 years ago
We don't use docker compose
to run PAWLS in production. We deploy the application to a centrally managed GKE cluster. That cluster provides authentication via oauth2-proxy in coordination with the Ingress NGINX Controller for Kubernetes.
In this case your application likely isn't working as toggling the environment variables only causes the API to expect authentication. The API layer doesn't handle handing unauthenticated clients off to an oauth provider -- oauth2-proxy normally takes care of that.
The setup we use is fairly complicated and likely not very appropriate for your use. Here's an idea for an alternative, that might be easier to setup:
docker compose
.The downside here is that after authenticating you're relying on the honor system as a way of preventing users from masquerading as one another. But that might be an acceptable trade-off, if you have a small number of users.
Hopefully this helps!
Thanks for the clarification!
Sure thing. I'm going to close this as I added some details and a suggested path for hosting things. Feel free to reopen it if you run into difficulties and I'll do my best to help!
It would be great if the docs were a little clearer on running the docker-compose in production.
I have changed the build ARGS and added environment variables. However, this doesn't seem to work.
Any idea on how to run with your own skiff login for OAuth?