Omnia-OmniCore/docker-compose.dev.yml at main · tanzim2000/Omnia-OmniCore · 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
# Identical to docker-compose.yml except it builds the image from the source
# in this folder instead of pulling a published one, so your local changes
# are what actually runs.
#
# The version reports as "dev", which is deliberate: a local build isn't a
# release, and OmniCore should never mistake it for one or try to "update"
# a work-in-progress out from under you.

services:
  omnicore:
    build:
      context: .
      args:
        OMNICORE_VERSION: dev

    container_name: omnicore-dev
    restart: unless-stopped

    ports:
      - "3000:3000"
      - "1303:1303"
      - "3999:3999"
      - "4000:4000"
      - "4001:4001"
      - "4002:4002"
      - "4003:4003"
      - "4004:4004"
      - "4005:4005"
      - "4006:4006"
      - "4007:4007"
      - "4008:4008"
      - "4009:4009"
      - "4010:4010"

      # Inports — see docker-compose.yml's own comment on this range
      - "2001:2001"
      - "2002:2002"
      - "2003:2003"
      - "2004:2004"
      - "2005:2005"
      - "2006:2006"
      - "2007:2007"
      - "2008:2008"
      - "2009:2009"
      - "2010:2010"

    volumes:
      # Separate volumes from the real install, so experimenting here can't
      # damage a working setup on the same machine.
      - omnicore-dev-data:/app/data
      - omnicore-dev-modules:/app/modules
      - omnicore-dev-themes:/app/themes

      # No docker.sock here on purpose. A dev build has nothing to update
      # itself to, so there is no reason to hand it control of the host.

volumes:
  omnicore-dev-data:
  omnicore-dev-modules:
  omnicore-dev-themes: