adl/docker-compose.dev.yml at main · wmo-raf/adl · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
# Overrides docker-compose.yml to build and run the `dev` target.
#
# Note the `image: adl:dev` on every service. The dev target deliberately does
# NOT contain the app source -- it is bind-mounted below -- so an image built
# from it is unusable as a base image for anything that does not also mount
# core. Plugins build `FROM adl:latest` and mount only themselves, so if the
# dev target were tagged `adl:latest` too, whichever of `make build` and
# `make dev-build` you ran last would decide whether every plugin's dev stack
# in every other repo could start. Two targets, two tags. See #252.

services:
  adl:
    image: adl:dev
    build:
      target: dev
    command: django-dev-no-attach
    environment:
      DEBUG: "True"
      MIGRATE_ON_STARTUP: "true"
      COLLECT_STATICFILES_ON_STARTUP: "true"
      VUE_FRONTEND_DEV_SERVER_URL: ${VUE_FRONTEND_DEV_SERVER_URL:-http://localhost:5173}
    volumes:
      - ./adl:/adl/app
    ports:
      - "8004:8000"

  adl_celery_worker_default:
    image: adl:dev
    build:
      target: dev
    command: celery-worker-dev
    environment:
      DEBUG: "True"
    volumes:
      - ./adl:/adl/app

  adl_celery_worker_adl:
    image: adl:dev
    build:
      target: dev
    command: celery-worker-adl
    environment:
      DEBUG: "True"
    volumes:
      - ./adl:/adl/app

  adl_celery_worker_dispatch:
    image: adl:dev
    build:
      target: dev
    command: celery-worker-dispatch
    environment:
      DEBUG: "True"
    volumes:
      - ./adl:/adl/app

  adl_celery_beat:
    image: adl:dev
    build:
      target: dev
    environment:
      DEBUG: "True"
    volumes:
      - ./adl:/adl/app