Getting Up and Running Locally¶
Setting Up Development Environment¶
Make sure to have the following on your host:
First things first.
Create a virtualenv:
$ python3.7 -m venv <virtual env path>
Activate the virtualenv you have just created:
$ source <virtual env path>/bin/activate
Install development requirements:
$ pip install -r requirements/local.txt
Create a new PostgreSQL database using createdb:
$ createdb <what you have entered as the project_slug at setup stage> -U postgres --password <password>
Set the environment variables for your database(s):
$ export DATABASE_URL=postgres://postgres:<password>@127.0.0.1:5432/<DB name given to createdb> # Optional: set broker URL if using Celery $ export CELERY_BROKER_URL=redis://localhost:6379/0
Check out the Settings page for a comprehensive list of the environments variables.
To help setting up your environment variables, you have a few options:
- create an
.envfile in the root of your project and define all the variables you need in it. Then you just need to have
DJANGO_READ_DOT_ENV_FILE=Truein your machine and all the variables will be read.
- Use a local environment manager like direnv
- create an
$ python manage.py migrate
See the application being served through Django development server:
$ python manage.py runserver 0.0.0.0:8000
Setup Email Backend¶
In order for the project to support MailHog it must have been bootstrapped with
use_mailhog set to
MailHog is used to receive emails during development, it is written in Go and has no external dependencies.
For instance, one of the packages we depend upon,
django-allauth sends verification emails to new users signing up as well as to the existing ones who have not yet verified themselves.
Download the latest MailHog release for your OS.
Rename the build to
Copy the file to the project root.
Make it executable:
$ chmod +x MailHog
Spin up another terminal window and start it there:
Check out http://127.0.0.1:8025/ to see how it goes.
Now you have your own mail server running locally, ready to receive whatever you send it.
If the project is configured to use Celery as a task scheduler then by default tasks are set to run on the main thread
when developing locally. If you have the appropriate setup on your local machine then set the following
CELERY_TASK_ALWAYS_EAGER = False
Sass Compilation & Live Reloading¶
If you’d like to take advantage of live reloading and Sass compilation you can do so with a little bit of preparation, see Sass Compilation & Live Reloading.
Congratulations, you have made it! Keep on reading to unleash full potential of Cookiecutter Django.