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
For the current PyNest examples, use config.py to construct the database provider and read environment-specific values from environment variables (.env for local development). For example, examples/OrmSyncApp/src/config.py calls load_dotenv() and reads SQLITE_DB_NAME via os.getenv. The async example follows the same pattern.
A development.yaml file is fine for non-secret defaults if your application chooses to load one, but PyNest does not currently prescribe or automatically load a development YAML configuration. For production, supply environment variables through your deployment environment and keep credentials out of committed YAML files. This is a recommendation based on the current examples, not a framework requirement.
Activity
ItayTheDar commentedon May 24, 2024
Hi! Not sure what is the dev yaml file you suggested, could you share more on that??
Allin2000 commentedon May 24, 2024
Environment-aware configuration.
What I mean by this is that configuration should be a best practice for a production environment.
ItayTheDar commentedon Sep 30, 2026
For the current PyNest examples, use
config.pyto construct the database provider and read environment-specific values from environment variables (.envfor local development). For example,examples/OrmSyncApp/src/config.pycallsload_dotenv()and readsSQLITE_DB_NAMEviaos.getenv. The async example follows the same pattern.A
development.yamlfile is fine for non-secret defaults if your application chooses to load one, but PyNest does not currently prescribe or automatically load a development YAML configuration. For production, supply environment variables through your deployment environment and keep credentials out of committed YAML files. This is a recommendation based on the current examples, not a framework requirement.