-
Notifications
You must be signed in to change notification settings - Fork 0
/
orderly-web.yml
93 lines (88 loc) · 3.17 KB
/
orderly-web.yml
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
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
## Prefix for container names; we'll use {container_prefix}_(orderly,web)
container_prefix: orderly_web
## The name of the docker network that containers will be attached to.
## If you want to proxy OrderlyWeb to the host, you will need to
## arrange a proxy on this network, or use dev_mode in the web section
## below.
network: orderly_web_network
## Names of the docker volumes to use:
##
## orderly: stores the orderly archive
## proxy_logs: stores logs from the reverse proxy (only used if proxy is given)
## css: stores compiled css for the web app (only needed if custom sass variables
## are given as sass_variables in web section below)
##
## (More volumes are anticipated as the tool develops)
volumes:
orderly: orderly_web_volume
proxy_logs: orderly_web_proxy_logs
css: orderly_web_css
## Orderly configuration
orderly:
## Image to use for orderly. This should build off of
## vimc/orderly.server but can be extended to use whatever packages
## you need. The components repo, image and tag will be assembled as
## <repo>/<name>:<tag> for the full docker image reference.
image:
repo: vimc
name: orderly.server
tag: master
## Api and Website configuration
admin:
image:
repo: vimc
name: orderly-web-user-cli
tag: master
web:
## Image to use for the web components. As for the orderly
## configuration these will be assembled as <repo>/<name>:<tag>. In
## addition, a second image with the database migration support will
## be used as <repo>/<migrate>:<tag>. It is not expected (unlike
## the orderly image) that the 'name' and 'migrate' will need to be
## changed often, and it is expected that a web image will go
## together with a corresponding migration image. If custom sass
## variables are provided below as sass_variables, a third image
## for generating css is required.
image:
repo: vimc
name: orderly-web
tag: mrc-275
migrate: orderlyweb-migrate
css-generator: orderly-web-css-generator
## If dev_mode is true then the port is exposed to the host (as
## plain http). Do not use in production. The port is attached
## only to the localhost and will not be available from other
## machines
dev_mode: true
## Port to use for the web service
port: 8888
## Name of the web service (affects the UI)
name: OrderlyWeb
## Email address of the web service
email: admin@example.com
## Authentication configuration
auth:
## Name of the github organisation if using github auth
github_org: vimc
## Name of the team within this github organisation if using
## github auth (cuurrently must be "" - VIMC
github_team: ""
## Enable or disable fine grained permissions
fine_grained: true
## Enable montagu authentication provider
montagu: false
## Optional sass variables to override default styles. Should be a
## file path relative to the config file
sass_variables: variables.scss
## If running a proxy directly, fill this section in. Otherwise you
## are responsible for proxying the application out of the docker
## network
proxy:
enabled: true
hostname: localhost
port_http: 80
port_https: 443
image:
repo: vimc
name: orderly-web-proxy
tag: mrc-211