journald or syslog https://docs.docker.com/compose/compose-file/#logging

Our next big milestone is to bring mypy support for all our projects.

Things that needs to be done:

• Installing mypy by default
• Adding typehints everywhere
• Installing stubs for django and other tools we use

pylint is quite brutal for CI process, but generating artifacts on the job is nice.
It allows to view all the stats about our code base.

Add PYTHONHASHSEED="random" to Dockerfile

Right now pipenv is broken.

http://www.structlog.org/en/stable/

For some reason Pipfile misses https://pypi.python.org/pypi/flake8-docstrings

Would our template benefit from moving apps into server/apps/ directory?

I can see several benefits:

• It would be easy to integrate coverage and pylint
• It would be easy to ingrate setup.py
• Cleaner directory structure

Cons:

• Not a default django structure

Here's how it should work:

• A new project is created via cookiecutter cli
• A docker-compose is spawned to run all tests inside this new project

Just delete www. part in Caddyfile.

After completing these steps

pip install pipsi
pipsi install pew
pipsi install pipenv

I can't execute

pipenv install -d

The result is :

command not found: pipenv

Right now security is configured in different places across the settings package.

Tasks:

• check that all settings from https://docs.djangoproject.com/en/1.8/ref/settings/#secure-browser-xss-filter present in the template
• think about django-security
• think about django-csp

Subtasks:

• run configurations
• pycharm docs

Right now pipenv is broken.

It will make it easier to integrate this stack with heroku.

And it might be useful, since we deploy to heroku sometimes.

In the productions settings we are missing:

• https://docs.djangoproject.com/en/1.11/ref/settings/#admins
• https://docs.djangoproject.com/en/1.11/ref/settings/#managers

I have never used it before, but this issue looks promising:
docker/compose#2092

We should include:

• our badge
• our link
• slogan
• authors

We need to test the most complex example:

• local development works
• development container works
• production container works

It would be also nice to:

• Run the default project's tests
• Run the default project's style checks
• Run the default project's QA

This can be achieved with https://github.com/hackebrot/pytest-cookies

There are some neat libraries:

• https://pypi.python.org/pypi/python-decouple
• https://github.com/mikeorr/Unipath

We will need this setting to be able to ping localhost for health checks.
Related #27

I will need to add a django-rest-framework example with jwt auth.

Deeper dive required: https://docs.docker.com/engine/security/trust/content_trust/#push-trusted-content

It's unclear how and when to use

pre-commit hooks

pre-commit install
pre-commit install -t commit-msg

They are described in Development process section

https://github.com/containous/traefik

https://docs.docker.com/engine/swarm/secrets/#defining-and-using-secrets-in-compose-files
https://docs.docker.com/compose/compose-file/#short-syntax-2

It would be also nice to provide an example with PG_PASSWORD variable.

Should we add explicit note about using overlay2 (or maybe other?) as a default driver for docker?

https://docs.docker.com/engine/userguide/storagedriver/overlayfs-driver/

We should also document why using this driver will benefit your project.

There are two options:

• enabling healthchecks in Dockerfile
• enabling healthchecks in docker-compose.yml

We need to investigate which one is better.

Docs:

• https://docs.docker.com/engine/reference/builder/#healthcheck
• https://docs.docker.com/compose/compose-file/#healthcheck

Pluggable app for django: https://github.com/KristianOellegaard/django-health-check
Good tutorial: http://codeblog.dotsandbrackets.com/docker-health-check/

The Given Info is a bit ambiguous for a newcomer.
It will be nice to add "Quick Start" Content , where all the steps are described.

When installing docker setting to n it really does not change anything:

• remove docs
• docker/ folder
• docker-compose.yml and .dockerignore

https://caddyserver.com/docs/automatic-https

HTTP Strict Transport Security (HSTS) is a web security policy mechanism which helps to protect websites against protocol downgrade attacks and cookie hijacking. Enabling HSTS declares that web browsers should only interact with the server using a secure HTTPS connection, and never via an insecure HTTP connection. The policy specifies a period of time during which the server must be accessed in a secure fashion.

Caddy does not enable HSTS by default, because if you wish to use the domain without HTTPS, HSTS having been enabled and remembered by a browser means the browser will not allow connections to your server. HSTS should only be enabled in a production environment when you know that you won't want to disable HTTPS in the future. It can easily be enabled by adding the header below to your Caddyfile.

header / Strict-Transport-Security "max-age=31536000;"

Right now we are serving static files from django.
That's not a right way to do it.

We need to use:

• https://caddyserver.com/docs/root
• https://docs.docker.com/compose/compose-file/#volumes

Hi 👊

This is my first visit to this fine repo, but it seems you have been working hard to keep all dependencies updated so far.

Once you have closed this issue, I'll create separate pull requests for every update as soon as I find one.

That's it for now!

Happy merging! 🤖

For some reason I have now started to receive segmentation fault errors in development. It does not happen all the time. Just happens at some unpredictable cases.

I have found two solutions (hacks):

1. Add --noreload option to runserver command
2. Add import threading; threading.stack_size(2*1024*1024) # noqa to the top level of manage.py

Waiting this issue to be fixed: https://bugs.alpinelinux.org/issues/8134
Also related: docker-library/python#211

https://pyup.io/

https://github.com/jazzband/silk/

Consider adding it alongside with drf and an example application.

Here's a good example: https://github.com/magfest/ubersystem-deploy/blob/master/README-pycharm.md

I would really like to get some support from @lk-geimfari

What needs to be done:

1. Add django-rest-framework #40
2. Add tests with mimesis

A fabric maybe?

Should it be included?
I guess, right now it is way too complex to implement and maintain.

https://www.youtube.com/watch?v=CteZol_7pxo&feature=youtu.be
https://about.gitlab.com/features/review-apps/

https://pip.pypa.io/en/stable/user_guide/#environment-variables

https://pypi.python.org/pypi/pytest-xdist

We need to create the document for closing a project (ltd)

Maybe, we should add restart: always to the docker-compose.prod.yml.
Now we are using restart-policy. But this only works with swarm.
Need to state this in docs.

Right now radon is a special beast. But it can be integrated into flake8 linting with