Repository navigation
Deploy the demo after a release - #19
Merged
Merged
Conversation
The demo on the VPS (docker compose, image tagged latest) was updated by hand. After the image is published it now pulls it and restarts, as the Ways' demos do; it can also be run by hand.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The demo at kododo.dev/polyglot/demo runs with docker compose on the VPS (
/opt/docker/polyglot-demo, imagelatest) and was updated by hand. This workflow pulls the image and restarts the service after Publish Docker image succeeds, the same way the Ways deploy their demos (VPS secrets of the organization). It can also be run by hand (workflow_dispatch). A pre-release does not movelatest, so it changes nothing on the demo.