You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Action can only be manually triggered. It would be best to automatically publish a :latest on all commits to master and tagged versions when you publish tags/releases (+ optionally a stable tag for the stable releases).
The text was updated successfully, but these errors were encountered:
Whenever a push is made to master in the backend or frontend repository, there is a push to dockerhub with latest
For the frontend repository, and extra latest-syc-base is also published, with the /syc/ backend settings.
When a release is made from the backend / frontend, an image tagged with the version number is published, as well as a prod tagged image.
In the frontend the syc-base versions are also included
This means that:
latest: latest master
prod: latest release
In this repository, for the image that combines both frontend and backend, it's similar but I will still trigger the releases by hand, just to make sure that both frontend and backend are in sync with each other, so you can use latest and prod as before, as well as the release tag. Also, the release contains info of the release tags of backend and frontend.
A bit confusing admittedly but I think the tags in docker-hub are self-explaining:
Currently the Action can only be manually triggered. It would be best to automatically publish a
:latest
on all commits tomaster
and tagged versions when you publish tags/releases (+ optionally astable
tag for the stable releases).The text was updated successfully, but these errors were encountered: