digitalbss/db-update repository overview

⁠MEF.DEV DB Update

Brings the MEF.DEV⁠ platform database on an existing SQL Server to the schema of a release — for servers that are not the lab image digitalbss/mssql⁠, or that already hold platform data. The image tag is the platform release it upgrades to.

⁠Role in the platform

Three steps against the server named by MSSQL_HOST and the database named by MSSQL_DB:

1. the pre-deployment script (sqlcmd);
2. publication of the platform schema (sqlpackage);
3. the post-deployment script, which gets the release number as APP_VERSION.

The container has no ports. When the three steps are done it stays idle rather than exiting — read the log, then stop and remove it.

⁠Run

docker run -d --name db-update \
  -e MSSQL_HOST=<server> -e MSSQL_DB=<database> \
  -e MSSQL_USER=<login> -e MSSQL_PASSWORD=<password> \
  -e APP_VERSION=<version> \
  digitalbss/db-update:<version>
docker logs -f db-update

Always pass the credentials at run time — the defaults inside the image are public. The job writes the login and the password it uses to its log: treat the log as a secret and remove the container afterwards. Back up the database before the upgrade.

⁠Learn more

• Platform Architecture⁠ — data tier and deployment patterns

⁠License

Business Source License 1.1⁠; each release converts to Apache License 2.0 on its Change Date. See Licensing⁠.