Skip to content

Fix a naming mismatch so that container deployments work #84

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Mar 14, 2024

Conversation

korlaxxalrok
Copy link
Collaborator

We use docker-compose in Actions to build certain services' container images. There is a necessity for a few parts of the service definition to share a similar name. Looks like this was modified at some point, the result being that we were building a container image with one image:tag, and then telling our webhook updater to use a different image:tag. So nothing was being deployed. This PR largely fixes that.

Additionally it adds some comments and bit of extra info in the README about the process.

…k to work as expected

- Update docker-compose.yaml to match service component naming so CI build-and-deploy process builds the expected container images and posts them correctly to the dployment webhook.
- Update docker-compose.yaml with additional comments.
- Update README.md with additional comments on build-and-deploy process.
@korlaxxalrok korlaxxalrok requested a review from BrainIsDead March 7, 2024 17:41
Copy link
Collaborator

@dmytrotsko dmytrotsko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Collaborator

@BrainIsDead BrainIsDead left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGFM

@BrainIsDead BrainIsDead merged commit 030d0f9 into development Mar 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants