Skip to content

Commit 89783f6

Browse files
Add info about latest image and minor fixes
1 parent 9f82b9c commit 89783f6

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

README.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,13 +9,19 @@ This repository contains a custom `mysql` docker image. Changes we have made:
99

1010
## Change DB via migrations
1111

12-
In order to change the DB image via DB migrations in https://github.com/serlo/db-migrations do the following:
12+
In order to change the DB image via DB migrations do the following:
1313

1414
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
1616
3. Check the changes in the DB via `make mysql`.
1717
4. Make a new dump via `make dump` and commit your changes.
1818

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+
1923
## Publish prereleases
2024

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.
26+
27+

0 commit comments

Comments
 (0)