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
Maybe it's worth noting that dockerhub provides a very convinient automation process for container builds. Is it possible for you @aquavitae to add this feature?
What is incomplete in this tutorial is versioned releases, which i would recommend so users don't get unintended updates. For the build rules, it could look like this:
This example config does the following:
Every commit on master -> rolled out to aquavitae/weasyprint:dev
Every release of a new version -> rolled out to aquavitae/weasyprint:latest
-> rolled out to aquavitae/weasyprint:{version}
Then, it's just necessary to make a new release in Github whenever a new version is released. This is as simple as:
The text was updated successfully, but these errors were encountered:
Hello there
looks like the Dockerfile was updated recently, but the changes aren't rolled out to docker hub (https://hub.docker.com/r/aquavitae/weasyprint/tags).
Maybe it's worth noting that dockerhub provides a very convinient automation process for container builds. Is it possible for you @aquavitae to add this feature?
Here is a tutorial for this.
What is incomplete in this tutorial is versioned releases, which i would recommend so users don't get unintended updates. For the build rules, it could look like this:
This example config does the following:
Then, it's just necessary to make a new release in Github whenever a new version is released. This is as simple as:
The text was updated successfully, but these errors were encountered: