eformat
commented
3 years ago I also like serving the docs locally in the cluster. You can
- quickfix them
- dont get any upstream changes whilst enablement running
https://github.com/eformat/enablement-docs/commit/c274275787f0c8a8f13d6c53181d03c81021a0cb
oc new-project enablement-docs
oc new-app quay.io/eformat/docsify-enablement:4.6 --as-deployment-config=true
oc expose dc/docsify-enablement --port=8080
oc create route edge docsify-enablement --service=docsify-enablement --port=8080 --hostname=enablement-docs.apps.dpc.apac-1.rht-labs.com
oc patch dc/docsify-enablement -p '{"spec":{"template":{"spec":{"containers":[{"name":"docsify-enablement","imagePullPolicy":"Always"}]}}}}'
oc scale dc/docsify-enablement --replicas=2
# make changes
cd ~/git/enablement-docs
make podman-push
oc tag quay.io/eformat/docsify-enablement:4.6 enablement-docs/docsify-enablement:4.6
Right now we have to remember to manually publish our changes after merging in changes to the exercises. Before we head down the path of full-fledged CICD, do we think it would be beneficial to at least have a minimal GH action that publishes our changes after merges? There's a handful of examples and should cost little effort to get this in place.