awesome-compose/django
Andy Madge a42a8531ab
Added --no-cache-dir option to all Python pip commands in Dockerfiles (#113)
The cache gives no benefit to a Docker image but it does add size, hence it's best left out.

Signed-off-by: Andy Madge <andymadge@gmail.com>
2021-03-22 10:01:41 +01:00
..
app Added --no-cache-dir option to all Python pip commands in Dockerfiles (#113) 2021-03-22 10:01:41 +01:00
docker-compose.yml Django example (#43) 2020-04-07 14:00:55 +02:00
README.md correct reference to number of containers 2020-07-27 22:26:00 -05:00

Compose sample application

Django application in dev mode

Project structure:

.
├── docker-compose.yml
├── app
    ├── Dockerfile
    ├── requirements.txt
    └── manage.py

docker-compose.yml

services: 
  web: 
    build: app 
    ports: 
      - '8000:8000'

Deploy with docker-compose

$ docker-compose up -d
Creating network "django_default" with the default driver
Building web
Step 1/6 : FROM python:3.7-alpine
...
...
Status: Downloaded newer image for python:3.7-alpine
Creating django_web_1 ... done

Expected result

Listing containers must show one container running and the port mapping as below:

$ docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED              STATUS              PORTS                    NAMES
3adaea94142d        django_web          "python3 manage.py r…"   About a minute ago   Up About a minute   0.0.0.0:8000->8000/tcp   django_web_1

After the application starts, navigate to http://localhost:8000 in your web browser:

Stop and remove the containers

$ docker-compose down