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 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
The text was updated successfully, but these errors were encountered:
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
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
The text was updated successfully, but these errors were encountered: