sixfeetup / sixienote

Demo Application for Training and Showing Best Practices

SixieNote in Django

Uses:

• Django 3.0
• Python 3.8

Getting Started using Docker

Clone this repository and you can start developing on the project using the following commands.

$ cp docker-compose.override.yml.example docker-compose.override.yml
$ make build-dev
$ docker-compose up

This will give you a running Postgres, Mailhog and a Django running under runserver_plus at http://localhost:8000. Start editing your code!

Getting Started with a Local Virtualenv

Clone the repo like above, but you will be responsible for setting up the database, a database user and the mailhog instance. You will also need to make sure you have Python 3.8 installed and use it to create your virtualenv.

Once you have all of that, you need to install the requirements files in the requirements/ folder for your specific situation (local dev or production).

On second thought, let's just make it easy on ourselves and the Docker way above.

sixienote's Issues

Run ASGI/Channels without runserver_plus

Hello,

I'm discovering Django and Channels, so first of all, thank you very much for this great tutorial !

As the 2020webinar branch contains the edited code during the video tutorial, the run command appears to not be set properly for local execution in Docker Compose. In the video the run configuration appears to be done in PyCharm but when we use docker compose directly, the "runserver_plus" should be disabled in docker-compose.yml.

So this line :

command: python manage.py runserver_plus 0.0.0.0:8000

should be replaced by :

command: python manage.py runserver 0.0.0.0:8000

Then everything starts properly and the async buttons work perfectly !

docker-compose up returns error

Followed directions in readme, all went well until the docker-compose step:

mike@t430sDebian:/files/django3/SixieNote$ docker-compose --verbose up
compose.config.config.find: Using configuration files: ./docker-compose.yml,./docker-compose.override.yml
ERROR: compose.cli.main.main: The Compose file is invalid because:
Service front-end has neither an image nor a build context specified. At least one must be provided.

docker images appear OK:

mike@t430sDebian:/files/django3/SixieNote$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
sixienote_local_django dev 29133ca2c5ec About an hour ago 525MB
python 3.8-slim e8ad3533cb52 5 days ago 194MB

mike@t430sDebian:/files/django3/SixieNote$ docker --version
Docker version 19.03.8, build afacb8b7f0

the host is Debian 10:
mike@t430sDebian:/files/django3/SixieNote$ cat /etc/debian_version
10.3

mike@t430sDebian:/files/django3/SixieNote$ uname -a
Linux t430sDebian 4.9.0-8-amd64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux

'make build-dev' succeeded:
...
Successfully built 29133ca2c5ec
Successfully tagged sixienote_local_django:dev

BTW, is it going to be possible to edit the Django code using PyCharm on the host with the application source code in the container? Thanks.

Error with make

After adding two new dependencies under main.in, I'm trying to make compile. But it shows the error below:

/bin/sh: 1: WORKS/WORKS/Django/SixieNote/requirements:/local: not found
make: *** [compile] Error 127

I don't know about Makefile :(
Just following along your session and stuck here :(