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
* create a new database (i.e. openIMIS.X.Y.Z where X.Y.Z is the openIMIS database version)
28
28
29
-
* Execute the initial database creation script fullEmpytDatabase.sql or fullDemoDatabase.sql (see "creating SQL script" section on how to get them)
29
+
* Execute the initial database creation script fullEmptyDatabase.sql or fullDemoDatabase.sql (see "creating SQL script" section on how to get them)
30
30
31
31
### Upgrading
32
32
33
-
In order to upgrade from the previous version of openIMIS database (see [Versioning](#versioning) section), execute the migration script (fullMigrationSript), see "creating SQL script" to get it
33
+
In order to upgrade from the previous version of openIMIS database (see [Versioning](#versioning) section), execute the migration script (fullMigrationScript), see "creating SQL script" to get it
SQL files for initialisaiton or update are created using bash script concatenate_files.sh or by downloading the sql-file zip from the latest release https://github.com/openimis/database_ms_sqlserver/releases/latest
46
+
SQL files for initialisation or update are created using bash script concatenate_files.sh or by downloading the sql-file zip from the latest release https://github.com/openimis/database_ms_sqlserver/releases/latest
-INIT_MODE if set to demo will init the database to demo (works only if not yet init)
59
+
-DEMO_DATASET if set to true will init the database to demo (works only if not yet init) otherwise comment it out
60
60
- SQL_SCRIPT_URL url to init scripts
61
61
-**ACCEPT_EULA** must be set to Y to accept MS SQL EULA
62
62
- SA_PASSWORD default: IMISuserP@s
63
-
- DB_USER_PASSWORD defautl: IMISuserP@s
64
-
-DB_NAMEdefautl: IMIS
65
-
- DB_USER defautl: IMISUser
63
+
- DB_USER_PASSWORD default: IMISuserP@s
64
+
-DB_NAME default: IMIS
65
+
- DB_USER default: IMISUser
66
66
67
67
68
68
### gettingstarted
@@ -79,15 +79,15 @@ docker build \
79
79
-t openimis-db
80
80
```
81
81
82
-
optinnaly
82
+
optional
83
83
```
84
84
--build-arg SQL_SCRIPT_URL=<url to the sql script to create the database> \
85
85
--build-arg DB_USER_PASSWORD=StrongPassword
86
86
--build-arg DB_USER=IMISUser
87
87
--build-arg DB_NAME=IMIS
88
88
```
89
89
***Notes***:
90
-
* by setting the ACCEPT_EULA=Y, you explicitely accept [Microsoft EULA](https://go.microsoft.com/fwlink/?linkid=857698) for the dockerized SQL Server 2017. Please ensure you read it and use the provided software according to the terms of that license.
90
+
* by setting the ACCEPT_EULA=Y, you explicitly accept [Microsoft EULA](https://go.microsoft.com/fwlink/?linkid=857698) for the dockerized SQL Server 2017. Please ensure you read it and use the provided software according to the terms of that license.
91
91
* choose a strong password (at least 8 chars,...)... or SQL Server will complain
92
92
93
93
@@ -97,13 +97,13 @@ To restore the backup inside the container:
97
97
98
98
99
99
***Note:***
100
-
the container will check if the database exist, if it doesnot it will take the latest demo release version and deploy it, SQL_SCRIPT_URL is per defautl set to "https://github.com/openimis/database_ms_sqlserver/releases/latest/download/sql-files.zip"
101
-
to have data retention when container are recreated volums need to be configured as microsoft docs suggest
100
+
The container will check if the database exist. If it does not, it will take the latest demo release version and deploy it, SQL_SCRIPT_URL is by default set to "https://github.com/openimis/database_ms_sqlserver/releases/latest/download/sql-files.zip"
101
+
To ensure data retention when containers are recreated, volumes need to be configured as suggested in the Microsoft documentation.
The database is writen within the container. If you want to keep your data between container execution, stop/start the container via `docker stop <CONTAINER ID>` / `docker start <CONTAINER ID>` (using `docker run ... ` recreates a new container from the image... thus without any data)
106
+
The database is written within the container. If you want to keep your data between container execution, stop/start the container via `docker stop <CONTAINER ID>` / `docker start <CONTAINER ID>` (using `docker run ... ` recreates a new container from the image, thus without any data)
0 commit comments