You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+22-24Lines changed: 22 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,8 @@
2
2
3
3
This repository provides a dockerized openIMIS (all components) as a quick setup for development, testing or demoing.
4
4
5
+
Please look for the direction on the openIMIS Wiki: https://openimis.atlassian.net/wiki/spaces/OP/pages/963182705/MO1.1+Install+the+modular+openIMIS+using+Docker
6
+
5
7
The docker-compose currently only contains the openIMIS database, backend, frontend and gateway components. It will be completed as the other components are added to the platform (batch platform,...)
6
8
7
9
| Disclaimer : NOT FOR PRODUCTION USE |
@@ -10,10 +12,16 @@
10
12
11
13
In case of troubles, please consult/contact our service desk via our [ticketing site](https://openimis.atlassian.net/servicedesk/customer).
12
14
15
+
#Prerequisit
16
+
- Windows 10 or Windows server 2016
17
+
- Docker installed and in Windows container mode
18
+
-
19
+
In case of troubles, please consult/contact our service desk via our [ticketing site](https://openimis.atlassian.net/servicedesk/customer).
20
+
13
21
# First startup
14
22
First startup is special since it will create the necessary docker images and containers to run openIMIS.
15
23
To build necessary, docker images, docker-compose relies on ***local*** docker files.
16
-
In order to build these images, you need to clone, next to `openimis-dist_dkr/` the following github repository:
24
+
In order to build these images, you need to clone, next to `openimis-dist_dkr/` the following github repository:branch:
From within `openimis-dist_dkr/windows` directory:
31
39
* create a `.env` file, providing the following variables:
32
40
```
33
-
#DB_SQL_SCRIPT=<URL pointing to the SQL script>
34
-
#ACCEPT_EULA=<must put Y but it means you accept Microsoft EULA for the MSSQL database container>
35
-
DB_HOST=<your database host, or db to use the demo docker 'db' service>
36
-
DB_PORT=<your database port on the host, 1433 if you use the demo docker 'db' service>
41
+
DB_SQL_SCRIPT=<URL pointing to the SQL script>
42
+
ACCEPT_EULA=<must put Y but it means you accept Microsoft EULA for the MSSQL database container>
43
+
DB_HOST=database
44
+
DB_PORT=1433
37
45
DB_NAME=<your database name, imis if you use the demo docker 'db' service>
38
46
DB_USER=<your database user, sa if you use the demo docker 'db' service >
39
47
DB_PASSWORD=<your database password, generate one if you use the demo docker 'db' service>
40
48
NEW_OPENIMIS_HOST=<(sub)domain under which the (new) openIMIS will be served (e.g. openimis.domaine) >
41
-
LEGACY_OPENIMIS_HOST=<(sub)domain under which legacy openIMIS is served (e.g. demo.openimis.org) >
49
+
LEGACY_OPENIMIS_HOST=frontend
42
50
```
43
51
44
52
* If you use the demo docker 'db' service:
45
53
* choose the SQL script to create/restore the database. Reference models are provided in [database_ms_sqlserver](https://github.com/openimis/database_ms_sqlserver) github. Example:
* build and start rest of the container (and backend) docker image: `docker-compose up`
54
63
(note: at each start, openIMIS will apply the necessary database migrations to update the database scheme)
55
-
* (if your are not working on localhost) register a letsencrypt certificate for your openIMIS gateway
56
-
* list running containers and spot the gateway: `docker container ls` (the gateway should be named `openimis-gateway`)
57
-
* connect to the gateway: `docker exec -it <CONTAINER ID> /bin/sh` (sh and not bash)
58
-
* issue the command `install-certificate.sh` ... and follow the setup wizzard (provide contact address,
59
-
* in case you are using your own computer and localhost NEW_OPENIMIS_HOST, running the lets encrypt script will activate the SSL but the SSL generation will fail, to solve this you can use self signed certificates
# in such context the database will not have enough memory, http://www.teamfoundation.co.za/2018/05/07/docker-linux-and-windows-event-more-3-from-containers-lcow/
0 commit comments