Note: This documentation is intentionally generic so that it can be copy-pasted between projects - do not put project specific details here.
The following diagram provides and overview of the core architecture components (Database, uwsgi server, web server):
The blue box is there to provide a means to develop on the same environment as you deploy and would not be relevant for server side deployments. Everything is managed using docker containers, with pycharm making ssh connections into the developer container and using the python interpreter found therein. Newer versions of PyCharm have 'native' docker support but after testing we opted to continue to use the ssh method described here. You may want to test when new versions of PyCharm come out in case they have improved the direct docker support.
Note: You don't need to use this architecture, you can deploy as a standard django app using virtualenv and locally installed postgis, nginx etc.
This image extends the production one, adding ssh to it. You must have built the production one first by following the "Quick Installation Guide"! When it's done, you can continue with this command:
Linux and MacOS:
make build-devweb
make devweb
cp docker-compose.override.example.yml docker-compose.override.yml
In case you don't get some not installed packages, you can run this repeatable steps:
- Close PyCharm
make kill
ordocker-compose -p projecta kill
make rm
ordocker-compose -p projecta rm
make build
make build-devweb
make devweb
- start PyCharm
If you're not using remote interpreter in PyCharm, skip step
7
and run:make devweb-runserver
to runserver in devweb container
Windows:
make-devbuild.bat
make-devweb.bat
Run test before you commit your modified files:
make test
or you can run test individually:
make flake8
`make coverage'
Open the project in pycharm then do:
- File -> Settings
- Project Interpreter
- Click on the gear icon next to project interpreter
- Add remote...
Now use these credentials:
- SSH Credentials (tick)
- Host: localhost
- Port: (use the ssh port specified in the docker-compose.yml file)
- User name: root
- Auth type: password (and tick 'save password')
- Password: docker
- Python interpreter path:
/usr/local/bin/python
When prompted about host authenticity, click Yes. After the python interpreter is set, set its path mapping:
- Local path:
<path to your git repo>/django_project
- Remote path:
/home/web/django_project
After that you should see something like this:
<Project root>/django_project→/home/web/django_project
In settings, django support:
-
tick to enable django support.
-
Set django project root to the path on your host that holds django code e.g.
<path to code base>/django_project
-
Set the settings option to your setting profile e.g.
core/settings/dev_docker.py
. If you need to use custom settings, copy this file e.g.dev_docker_tim.py
and place your modifications in your personalised copy. The first import of your custom file should import from dev_docker. -
manage script (leave default)
- Run -> Edit configurations
- Click the
+
icon in the top left corner - Choose
Django server
from the popup list
Now set these options:
- Name: Django Server
- Host: 0.0.0.0
- Port: (use the http port specified in the docker-compose.yml file, e.g. 8080)
- Run browser If checked, it will open the url after you click run. You should be able to access the running projecta on 0.0.0.0:61202 (the port that mapped to 8080)
- Additional options:
--settings=core.settings.dev_docker
- Run browser: Optionally set this to your IP address (MacOS/Linux) or your specific IP address (Windows) followed by the port forward address for port 8080 specified in your
docker-compose.yml
file. For example:http://0.0.0.0:61202
. - Environment vars: Leave as default unless you need to add something to the env
- Python interpreter: Ensure it is set you your remote interpreter (should be set to that by default)
- Interpreter options: Leave blank
- Path mappings: Here you need to indicate path equivalency between your host
filesystem and the filesystem in the remote (docker) host. Click the ellipsis
and add a run that points to your git checkout on your local host and the
/home/web directory in the docker host. e.g.
- Local path: /django_project
- Remote path: /home/web/django_project
- click OK to save your run configuration
Now you can run the server using the green triangle next to the Django server label in the run configurations pull down. Debug will also work and you will be able to step through views etc as you work.
I made a general overview screencast describing this process here:
Tim write stuff here....
To configure OAuth application on Github, go to https://github.com/settings/developers and click on your project or create a new project at https://github.com/settings/applications/new
It is mandatory to fill out Application Name, Homepage URL, and Authorization callback URL:
-
Application Name: changelog.kartoza.com
-
Homepage URL: https://changelog.kartoza.com
-
Authorization callback URL: https://changelog.kartoza.com/accounts/github/login/callback/
Click the Update application
button and generate Client secret by click on Generate a new client secret
button.
Now you have Client ID
and Client Secret
Go to django admin site: Home > Sites > Sites, and click on Add Site
button:
Go to django admin site: Home > Social Accounts > Social applications and Add social application
button:
-
Provider: Github
-
Client id: your
Client ID
-
Secret key: your
Client secret
-
Choosen sites: changelog.kartoza.com
Go to your website, login with Github and you'll be redirected to the Github authorize page.
Q: I get ImportError: Could not import settings core.settings.dev_docker
when starting the server.
A: django_project/core/settings/secret.py is either corrupt or you don't have permissions to read it as the user you are running
runserver`` as. A
common cause of this is if you are running the server in both production
mode and developer mode on the same host. Simply remove the file or change
ownership permissions so that you can read/write it.