-
Notifications
You must be signed in to change notification settings - Fork 6
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
[Recognizer] Setup CD #29
Conversation
55d19a8
to
17b981b
Compare
f052232
to
f6a60ac
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the __CI__...
a convention?
- name: Checkout the code | ||
uses: actions/checkout@v4 | ||
with: | ||
sparse-checkout: ${{ inputs.app-name }} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't really need that, do we? The tag is present in the github
context, and the container image is pulled from the registry
@LVala Github workflows cannot be nested so I prefixed them with |
Fixed |
After this PR, a new docker Recognizer docker image will be created, published and deployed every time we create a tag
recognizer-vX
whereX
can be anything e.g.v0.1.0
v0.1.0-32dfeg
v0.1.0-dev
.Docker image can be pulled with
docker pull ghcr.io/elixir-webrtc/apps/recognizer:0.1.0
(so withv
stripped) or usinglatest
.Deployed version is available under https://recognizer.elixir-webrtc.org