Skip to content
This repository has been archived by the owner on Jan 30, 2023. It is now read-only.

split settings into base, develop, production #5

Merged
merged 1 commit into from
Feb 18, 2021
Merged

Conversation

samuel-iseli
Copy link
Collaborator

implements multiple settings from #4

'ENGINE': 'django.db.backends.postgresql',
'NAME': 'depot-commun',
'USER': 'postgres',
'PASSWORD': 'password',
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'll have to think about removing passwords and so on for production in the future.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure. Passwords and secret key are properties that should be specified on the server. I think heroku has means to do this. That's what the heroku client library that we are using is meant for isn't it?

@samuel-iseli samuel-iseli merged commit 60d2c35 into main Feb 18, 2021
@samuel-iseli samuel-iseli deleted the split_settings branch February 18, 2021 20:29
@@ -128,5 +127,3 @@

STATIC_URL = '/static/'

django_heroku.settings(locals())
Copy link
Owner

@zuckerruebe zuckerruebe Feb 18, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we not also remove the DATABASES= part in base.py?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes that would make it consistent.
will you make the change or should I?

@samuel-iseli samuel-iseli linked an issue Feb 20, 2021 that may be closed by this pull request
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Different settings for development and production
2 participants