feat: Setup Helios deployment #67
Draft
+675
−97
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ntation (`compose.yaml` over `docker-compose.yaml`)
egekocabas
had a problem deploying
to
production
GitHub Actions
Failure
egekocabas
had a problem deploying
to
production
GitHub Actions
Failure
egekocabas
had a problem deploying
to
production
GitHub Actions
Failure
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
This PR includes necessary Github Actions & config changes for the Helios deployment. Initially, we will only build & deploy to production whenever a commit pushes to the main branch. The build version for microservices will be set as
latest, but when we decide on the versioning and other deployment strategies (deployment to dev), the actions will be updated.Description
prodandlocaldevelopment docker-compose files ascompose.yamlfor local developmentcompose.prod.yamlfor production