chore: remove Kraken hosting leftovers - #673
Merged
Merged
Conversation
Docs now deploy to Vercel via CI (#670) and docs.inkonchain.com has cut over. Remove the unused Dockerfile, .dockerignore, amplify.yml and the docker-publish job, and serialize production deploys with a concurrency group.
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.
What
Now that docs.inkonchain.com serves from the foundation Vercel account (#670), this removes the dead hosting config:
Dockerfileand.dockerignore(image was only consumed by Kraken's cluster)amplify.yml(leftover from an even earlier hosting life)docker-publishCI job (publishedghcr.io/inkonchain/docs:latestwhich nothing pulls anymore)Also adds a
concurrencygroup tovercel-deployso two quick merges can't complete out of order and briefly promote an older commit.Safe because
DNS cut over earlier today and Kraken's deployment is being decommissioned. Stopping image publishes doesn't affect anything still running.