In config.yml, certain fields such as USERS_SERVERADMIN_PASSWORD need to be hard coded. It would be nice if these fields could be left blank in the case that the corresponding env var is found on startup. Currently pangolin throws: Error: Invalid configuration file: Validation error, which is the expected behavior, but something like lazy loading would be an elegant fix for this.
Originally created by @jackrosenberg on GitHub (Jun 24, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/963
In `config.yml`, certain fields such as `USERS_SERVERADMIN_PASSWORD` need to be hard coded. It would be nice if these fields could be left blank in the case that the corresponding `env` var is found on startup. Currently pangolin throws: `Error: Invalid configuration file: Validation error`, which is the expected behavior, but something like lazy loading would be an elegant fix for this.
@jackrosenberg commented on GitHub (Jun 25, 2025):
Thanks for the fast response, I can PR this myself sometime in the coming weeks :)
<!-- gh-comment-id:3005205906 -->
@jackrosenberg commented on GitHub (Jun 25, 2025):
Thanks for the fast response, I can PR this myself sometime in the coming weeks :)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @jackrosenberg on GitHub (Jun 24, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/963
In
config.yml, certain fields such asUSERS_SERVERADMIN_PASSWORDneed to be hard coded. It would be nice if these fields could be left blank in the case that the correspondingenvvar is found on startup. Currently pangolin throws:Error: Invalid configuration file: Validation error, which is the expected behavior, but something like lazy loading would be an elegant fix for this.@oschwartz10612 commented on GitHub (Jun 25, 2025):
Good point this should be a simple fix we could add soon!
@jackrosenberg commented on GitHub (Jun 25, 2025):
Thanks for the fast response, I can PR this myself sometime in the coming weeks :)
@oschwartz10612 commented on GitHub (Jun 26, 2025):
That would be great!
@jackrosenberg commented on GitHub (Jun 30, 2025):
Think this is closed by 1.6.0, right? @oschwartz10612
@miloschwartz commented on GitHub (Jul 1, 2025):
@jackrosenberg Yep! We removed the need for these variables in 1.6
@jackrosenberg commented on GitHub (Jul 1, 2025):
Nice, good one!