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

Split settings file into separate settings for dev and production environment #4

Open
hamaMk opened this issue Jul 19, 2023 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@hamaMk
Copy link

hamaMk commented Jul 19, 2023

Separating settings allows for easy handling of configurations based on the environment e.g. SQLite database connection in development and Postgres in production.

@terrameijar
Copy link
Owner

Separating settings allows for easy handling of configurations based on the environment e.g. SQLite database connection in development and Postgres in production.

Yes, thank you for creating this issue @hamaMk . I want us to think about the best approach to do this, do you have any suggestions?

@hamaMk
Copy link
Author

hamaMk commented Jul 20, 2023

Yes first of all we replace the standard settings file with a module, then we create a base.py file that will contain common settings. We can now go on to create two more files dev.py and prod.py that will extend base.py. Voila.

@terrameijar
Copy link
Owner

Understood @hamaMk , please work on it and make a PR once you're done

Yes first of all we replace the standard settings file with a module, then we create a base.py file that will contain common settings. We can now go on to create two more files dev.py and prod.py that will extend base.py. Voila.

@terrameijar terrameijar added the enhancement New feature or request label Sep 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants