search

yeldiRium / st3k101

UNMAINTAINED.
2 stars 1 forks source link

work on semver #23

Open yeldiRium opened 5 years ago

yeldiRium commented 5 years ago

We want to use semver.

We currently have separate version files for the services in their respective folders and intend to keep them up to date conforming with semver.

However this makes it difficult to version the repository with tags.

We could either use service specific version tags (e.g frontend-2.0.1) or, we could split the repo as discussed a few times and version each repository.

The latter would include a rewrite of our ci system and an external docker-compose config.

strangedev commented 5 years ago

I'm all for the repo split. We would then have a separate repository containing the docker-compose.yml and possibly integration tests.

How would this setup work for services which themselves consist of multiple containers, for example xapi-publisher?

yeldiRium commented 5 years ago

I'd say leave together what belongs together. We can version e.g. backend and our custom postgres container together, since it is one service.

I like the idea of having a separate integration repo with additional tests.

strangedev commented 5 years ago

Split repositories