@@ -294,7 +294,6 @@ You will log in into`/home/eox/data` directory which contains the 2 logging dir
**NOTE:** The mounted directory that you are directed into is *`/home/user`*, where `user` is the username, hence when setting / editing the username in configs, the `sftp` mounted volumes path in `docker-compose.<collection>.yml` must change respectively.
# Documentation
## Installation
...
...
@@ -323,6 +322,19 @@ The documentation is generated in the respective *_build/html* directory.
# Create software releases
## Release a new vs version
We use [bump2version](https://github.com/c4urself/bump2version) to increment versions of invividual docker images and create git tags. Tags after push trigger CI `docker push` action of versioned images. It also updates used image versions in `.ops` docker compose files.
Pushing to `master` branch updates `latest` images, while `staging` branch push updates `staging` images.
For **Versions* in general, we use semantic versioning with format {major}.{minor}.{patch}-{release}.{build}.
First check deployed staging version on staging platform (TBD), then if no problems are found, proceed.
Following operation should be done on `staging` branch.
```
bump2version <major/minor/patch/release/build>
git push
git push --tags
```
Then `staging` branch should be merged to `master`, unless only a patch to previous versions is made.