Getting a local Seamless Auth environment running currently means setting up Postgres and roughly 41 environment variables by hand, including generated secrets (`TOTP_SECRET_ENCRYPTION_KEY`, `REFRESH_TOKEN_LOOKUP_SECRET`, `OAUTH_STATE_SECRET`). That is the main barrier to trying the project.
A compose file here that brings up Postgres and the API together, with sensible development defaults, would make local setup a single command. It could optionally include the admin dashboard (ghcr.io/fells-code/seamless-auth-admin-dashboard) pointed at the API, or rely on SERVE_ADMIN_DASHBOARD to serve it at /console.
Raised from a review of the dashboard repository, where the equivalent issue (fells-code/seamless-auth-admin-dashboard#98) was closed because the composition belongs with the API rather than duplicated downstream.
Getting a local Seamless Auth environment running currently means setting up Postgres and roughly 41 environment variables by hand, including generated secrets (`TOTP_SECRET_ENCRYPTION_KEY`, `REFRESH_TOKEN_LOOKUP_SECRET`, `OAUTH_STATE_SECRET`). That is the main barrier to trying the project.
A compose file here that brings up Postgres and the API together, with sensible development defaults, would make local setup a single command. It could optionally include the admin dashboard (
ghcr.io/fells-code/seamless-auth-admin-dashboard) pointed at the API, or rely onSERVE_ADMIN_DASHBOARDto serve it at/console.Raised from a review of the dashboard repository, where the equivalent issue (fells-code/seamless-auth-admin-dashboard#98) was closed because the composition belongs with the API rather than duplicated downstream.