Replies: 1 comment
-
I don't know what's best. Would an all-in-one solution be easier to get approval to be added to TrueCharts, as it will run on Kubernetes? Is this something your thinking of doing? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi everyone,
I'm opening this discussion in order to get some ideas about handling the versioning strategy for the project.
The project consists of a single Docker container running two services: a server and a web app. Initially, these services were split into two separate images, but to simplify the deployment process, they were merged them into one container.
We're approaching the release of the "first official" version,
1.0.0
, which will include both the web app and the server, each marked as version1.0.0
.I'm seeking advice on how to handle the versioning system moving forward. If the web app and server were in separate repositories, versioning would be straightforward: each would follow semantic versioning independently, and the repository version would match the respective service version.
However, with both services in the same repository, versioning becomes more complex. I’ve done some research to see how other projects manage this, such as a discussion on the Immich project (see here). They said that they are still in a fast development cycle and thus use versioning to track progress, planning for more strict versioning rules upon reaching a stable release. So not really something useful for now.
Other related discussions on Stack Overflow provide insights too:
One straightforward solution is to update both components synchronously. For example, if a new release (
1.0.1
) includes a fix only for the web app, both the web app and server would be versioned as1.0.1
(even though the server version1.0.1
is identical to1.0.0
).Pros:
Cons:
I believe this might be the preferred approach, but I’m open to suggestions. If you have any other ideas or best practices for handling this kind of versioning in a combined repository setup, please share them below. Your insights will be greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions