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
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,13 +9,19 @@ This repository contains a custom `mysql` docker image. Changes we have made:
9
9
10
10
## Change DB via migrations
11
11
12
-
In order to change the DB image via DB migrations in https://github.com/serlo/db-migrationsdo the following:
12
+
In order to change the DB image via DB migrations do the following:
13
13
14
14
1. Run MySQL DB in this repository with `make up`.
15
-
2. Run DB migrations in `db-migrations`, e.g. via `yarn migrate:run`.
15
+
2. Run DB migrations
16
16
3. Check the changes in the DB via `make mysql`.
17
17
4. Make a new dump via `make dump` and commit your changes.
18
18
19
+
## Publish Image
20
+
21
+
In order to automatically create the latest image, change the version at file `VERSION` and merge into `main` will.
22
+
19
23
## Publish prereleases
20
24
21
-
In order to publish a prerelease push to a branch with a name starting with `prerelease`. Then an image with a tag similar to the branch name is published. When you for example an image to a branch named `prerelease-feature1` an image is created which you can access via `eu.gcr.io/serlo-shared/serlo-mysql-database:prerelease-feature1`. This is for example useful when you need DB migrations in order to develop a new feature.
25
+
In order to publish a prerelease push to a branch with a name starting with `prerelease`. Then an image with a tag similar to the branch name is published. For example: a remote branch name like `prerelease-feature1` will created an image which you can access via `ghcr.io/serlo/serlo-mysql-database:prerelease-feature1`. This is for example useful when you need DB migrations in order to develop a new feature.
0 commit comments