Please keep in mind that if you are already using a Django project, your requirements may vary. This tutorial recommends a specific project structure, but you can also utilize each section of the tutorial separately based on your needs.<\/div>\n<\/div>\n
First, we need to reorganize Django’s settings.<\/h2>\n
First, to ensure the security of your Django project, you must navigate to the project directory and activate the virtual environment.<\/p>\n
<\/code><\/pre>\n\n- cd<\/span> django-apps<\/li>\n
- .<\/span> env\/bin\/activate<\/li>\n<\/ol>\n
<\/code><\/pre>\n <\/p>\n
<\/code><\/pre>\nTo begin, you will initially reorganize your settings.py file to cater to specific environments. This is a recommended approach when transferring a project across various environments such as development and production. By adopting this setup, you will minimize the need for extensive reconfiguration in different environments. Instead, you will utilize an environment variable to toggle between configurations, which will be covered in detail later in the tutorial.<\/p>\n
Make a settings directory within the subdirectory of your project.<\/p>\n
<\/code><\/pre>\n\n- mkdir<\/span> testsite<\/mark>\/testsite<\/mark>\/settings<\/li>\n<\/ol>\n
<\/code><\/pre>\n <\/p>\n
<\/code><\/pre>\n(According to the requirements, this tutorial utilizes testsite, but you have the option to substitute it with your project’s name.)<\/p>\n
The current settings.py file will be substituted by this directory, and all the environment-specific settings will be stored in individual files within this folder.<\/p>\n
In the folder for your new settings, make three Python files.<\/p>\n
<\/code><\/pre>\n\n- cd<\/span> testsite<\/mark>\/testsite<\/mark>\/settings<\/li>\n
- touch<\/span> base.py development.py production.py<\/li>\n<\/ol>\n
<\/code><\/pre>\n <\/p>\n
<\/code><\/pre>\nThe development.py file will include settings typically used while developing, while the production.py file will include settings meant for a production server. It is necessary to keep them separate as the production configuration will have settings that won’t function in a development environment, such as enforcing HTTPS, adding headers, and utilizing a production database.<\/p>\n
The base.py file will include settings that both development.py and production.py will derive from. This is done to decrease repetition and maintain code organization. As a result, you can eliminate the settings.py file to avoid any confusion with Django.<\/p>\n
When you are in the settings directory, use the following command to rename settings.py as base.py:<\/p>\n
<\/code><\/pre>\n\n- mv<\/span> ..<\/span>\/settings.py base.py<\/li>\n<\/ol>\n
<\/code><\/pre>\n <\/p>\n
<\/code><\/pre>\nYou have just finished outlining your newly created directory for environment-based settings. However, your project is not yet familiar with this new configuration. Therefore, your next step will be to address this issue.<\/p>\n
Step 2 involves the utilization of django-environ.<\/h2>\n
At present, Django is unaware of your new settings directory and its internal files. Therefore, in order to proceed with working on your environment-specific settings, you must configure Django to function with django-environ. django-environ is a necessary component that retrieves environment variables from a .env file. This implies that Django will examine a .env file located in your project’s main directory to determine the settings configuration to utilize.<\/p>\n
To view the contents of the directory, navigate to the main folder of your project and run the ls command.<\/p>\n
<\/code><\/pre>\n\n- cd<\/span> ..<\/span>\/..<\/span>\/<\/li>\n
- ls<\/span><\/li>\n<\/ol>\n
<\/code><\/pre>\n <\/p>\n
<\/code><\/pre>\nYour project’s main folder should have files organized in this manner.<\/p>\n
<\/code><\/pre>\nOutput<\/div>\n
<\/code><\/pre>\ndb.sqlite3 manage.py testsite<\/p>\n
<\/code><\/pre>\nYou should install django-environ.<\/p>\n
<\/code><\/pre>\n\n- pip install<\/span> django-environ<\/li>\n<\/ol>\n
<\/code><\/pre>\n <\/p>\n
<\/code><\/pre>\nTo utilize .env in Django, you must configure it. This can be achieved by making changes in two files: manage.py, for development purposes, and wsgi.py, for production purposes.<\/p>\n
Begin by accessing manage.py for modification using nano or any text editor of your choice.<\/p>\n
<\/code><\/pre>\n\n- nano<\/span> manage.py<\/li>\n<\/ol>\n
<\/code><\/pre>\n <\/p>\n
<\/code><\/pre>\nPlease include the code that is highlighted.<\/p>\n
manage.py in the testsite directory.<\/div>\n
import<\/span> os\r\nimport<\/span> sys\r\n<<\/span>^<\/span>><\/span>import<\/span> environ\r\n\r\nenviron.<\/span>Env.<\/span>read_env(<\/span>)<\/span><<\/span>^<\/span>><\/span>\r\n\r\ndef<\/span> main<\/span>(<\/span>)<\/span>:<\/span>\r\n os.<\/span>environ.<\/span>setdefault(<\/span>'DJANGO_SETTINGS_MODULE'<\/span>,<\/span> 'testsite.settings'<\/span>)<\/span>\r\n\r\n try<\/span>:<\/span>\r\n from<\/span> django.<\/span>core.<\/span>management import<\/span> execute_from_command_line\r\n except<\/span> ImportError as<\/span> exc:<\/span>\r\n raise<\/span> ImportError(<\/span>\r\n \"Couldn't import Django. Are you sure it's installed and \"<\/span>\r\n \"available on your PYTHONPATH environment variable? Did you \"<\/span>\r\n \"forget to activate a virtual environment?\"<\/span>\r\n )<\/span> from<\/span> exc\r\n execute_from_command_line(<\/span>sys.<\/span>argv)<\/span>\r\n\r\n\r\nif<\/span> __name__ ==<\/span> '__main__'<\/span>:<\/span>\r\n main(<\/span>)<\/span>\r\n<\/code><\/pre>\nTo save and close manage.py, press CTRL+X, choose Y to save, and press ENTER.<\/p>\n
To begin, open the file wsgi.py for editing.<\/p>\n
<\/code><\/pre>\n\n- nano<\/span> testsite<\/mark>\/wsgi.py<\/li>\n<\/ol>\n
<\/code><\/pre>\n <\/p>\n
<\/code><\/pre>\nInclude the specified highlighted sentences.<\/p>\n
Please provide a valid context or sentence containing “testsite\/testsite\/wsgi.py” so that I can paraphrase it accurately.<\/div>\n
\r\nimport<\/span> os\r\n<<\/span>^<\/span>><\/span>import<\/span> environ\r\n\r\nenviron.<\/span>Env.<\/span>read_env(<\/span>)<\/span><<\/span>^<\/span>><\/span>\r\n\r\nfrom<\/span> django.<\/span>core.<\/span>wsgi import<\/span> get_wsgi_application\r\n\r\nos.<\/span>environ.<\/span>setdefault(<\/span>'DJANGO_SETTINGS_MODULE'<\/span>,<\/span> 'testsite.settings'<\/span>)<\/span>\r\n\r\napplication =<\/span> get_wsgi_application(<\/span>)<\/span>\r\n<\/code><\/pre>\nTo save and close the file, you can use the key combination CTRL+X, followed by the letter Y to save, and finally press ENTER.<\/p>\n
The code added to these files performs two tasks. Firstly, it instructs Django to always refer to the .env file whenever it runs, be it through manage.py for development or wsgi.py for production. If the .env file exists, Django will use the settings file that .env suggests; otherwise, it will default to the development configuration.<\/p>\n
In the end, you will generate a .env file in the existing folder.<\/p>\n
<\/code><\/pre>\n\n- nano<\/span> .env<\/li>\n<\/ol>\n
<\/code><\/pre>\n <\/p>\n
<\/code><\/pre>\nNow include the following code to establish the environment as development:<\/p>\n
The environment variables of the testing site can be found at testsite\/.env.<\/div>\n
DJANGO_SETTINGS_MODULE=\"testsite<\/mark>.settings.development\"\r\n<\/code><\/pre>\nTo save and close the file, use the keyboard shortcut CTRL+X, press Y to save, and finally press ENTER.<\/p>\n
\n
Note<\/p>\n
Make sure to exclude the .env file from your commits by adding it to your .gitignore file. This file is meant to store sensitive data like passwords and API keys that should not be visible to the public. Each environment your project runs on should have its own .env file with specific settings for that environment. To make it easier to create a new .env file whenever needed, it is advisable to include a .env.example file in your project.<\/div>\n<\/div>\n
So, by default, Django will utilize testsite.settings.development. However, if you modify DJANGO_SETTINGS_MODULE to testsite.settings.production, for instance, it will begin using your production setup. Afterward, you need to fill in the configurations for development.py and production.py in your settings.<\/p>\n
Step 3 – Establishing Development and Production Configurations<\/h2>\n
Afterward, proceed to access your base.py and incorporate the necessary changes for each environment by creating the separate development.py and production.py files. It is essential to have your production database credentials readily accessible for the production.py file.<\/p>\n
\n
Note<\/p>\n
Please determine the necessary configuration settings based on your environment. This tutorial will only provide an example for production and development settings, including security settings and separate database configurations.<\/div>\n<\/div>\n
To demonstrate the process, we will be using the Django project mentioned in the previous tutorial. In order to transfer the settings, we will start by accessing the development.py file.<\/p>\n
<\/code><\/pre>\n\n- nano<\/span> testsite<\/mark>\/settings\/development.py<\/li>\n<\/ol>\n
<\/code><\/pre>\n <\/p>\n
<\/code><\/pre>\nNext, include the given code.<\/p>\n
\n
One possible paraphrase of “testsite\/testsite\/settings\/development.py” could be:<\/p>\n
– development.py file located within the testsite\/settings directory on testsite.<\/p>\n<\/div>\n
import<\/span> os\r\nfrom<\/span> .<\/span>base import<\/span> *<\/span>\r\n\r\nDEBUG =<\/span> True<\/span>\r\n\r\nDATABASES =<\/span> {<\/span>\r\n 'default'<\/span>:<\/span> {<\/span>\r\n 'ENGINE'<\/span>:<\/span> 'django.db.backends.sqlite3'<\/span>,<\/span>\r\n 'NAME'<\/span>:<\/span> os.<\/span>path.<\/span>join(<\/span>BASE_DIR,<\/span> 'db.sqlite3'<\/span>)<\/span>,<\/span>\r\n }<\/span>\r\n}<\/span>\r\n<\/code><\/pre>\nTo save and exit the file, press CTRL+X, followed by pressing Y to save, and finally hit ENTER.<\/p>\n
Initially, you will bring in the content from base.py, which inherits the settings from that file. Subsequently, you will adjust the desired settings specifically for the development environment. These settings include DEBUG, which should be set to True during development, but not in production; and DATABASES, which should be a local database instead of a production database. For development purposes, you will be utilizing an SQLite database.<\/p>\n
\n
Note<\/p>\n
To protect against revealing secrets, Django’s DEBUG output will never show certain settings that contain sensitive strings like API, KEY, PASS, SECRET, SIGNATURE, or TOKEN. This measure is in place to prevent the exposure of secrets if a project is mistakenly deployed in production with DEBUG still active. Therefore, it is strongly advised not to publicly deploy a project with DEBUG enabled as it can only compromise the security of the project.<\/div>\n<\/div>\n
Afterwards, you will make additions to production.py. Access the file by utilizing the given command:<\/p>\n
<\/code><\/pre>\n\n- nano<\/span> testsite<\/mark>\/settings\/production.py<\/li>\n<\/ol>\n
<\/code><\/pre>\n <\/p>\n
<\/code><\/pre>\nNext, include the subsequent code. The final output will resemble development.py; however, it will have an altered database configuration and DEBUG will be deactivated.<\/p>\n
production.py in testsite\/testsite\/settings<\/div>\n
import<\/span> os\r\n