Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ship oidc as two images, debug and prod #470

Open
spruce-bruce opened this issue Apr 24, 2020 · 0 comments
Open

Ship oidc as two images, debug and prod #470

spruce-bruce opened this issue Apr 24, 2020 · 0 comments
Labels
spike Research only to look into the implementation methods, risks, and level of effort for upcoming issue

Comments

@spruce-bruce
Copy link
Collaborator

spruce-bruce commented Apr 24, 2020

The prod image can be optimized, and the debug image can contain a bunch of utilities for debugging things.

The debug image could also potentially be used to work on oidc - like you could edit the code inside the container and commit/push to the oidc repo without having to set up a special odic dev environment. I think this could make it more fluid to work on oidc as part of normal project work

Debug Image Utilities

# Prints the oidc configuration environment variables
docker-compose exec oidc npm run debug:print-env

### Client utilities... these might even go on the prod image idk

# Makes a client. Uses reasonable defaults. Maybe takes some args for name, etc
docker-compose exec oidc npm run debug:client:create
# Prints the client objects to the console
docker-compose exec oidc npm run debug:client:print
@spruce-bruce spruce-bruce added the spike Research only to look into the implementation methods, risks, and level of effort for upcoming issue label Apr 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spike Research only to look into the implementation methods, risks, and level of effort for upcoming issue
Projects
None yet
Development

No branches or pull requests

1 participant