chore(just): add export and deploy recipes - #8
Merged
Merged
Conversation
`just deploy` builds the Mintlify static export and publishes it to Cloudflare Workers static assets. `just export` is split out as its own recipe and declared as a dependency, so you can build the export without deploying — worth having when you want to check what actually ships. Workers rather than Pages: Cloudflare's guidance is now "if you are starting a new project, use Workers instead of Pages", and static-asset requests on Workers are unmetered. The whole estate is moving to the same shape. `mint export` produces a real pre-rendered static build — I verified 27 pages with server-rendered HTML, and it needs no Mintlify account. Note this does mean giving up Mintlify's hosted search, analytics and AI chat, which are server-side; connecting the repo in their dashboard instead is the alternative.
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
2 participants
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.
Adds
just deployandjust exportso publishing is one command instead of a three-step incantation.exportis a separate recipe declared as a dependency ofdeploy, so you can build and inspect what would ship without publishing it.Workers, not Pages — Cloudflare's guidance is now "if you are starting a new project, use Workers instead of Pages", and static-asset requests on Workers are unmetered. The whole estate moves to the same shape.
I verified
mint exportproduces a genuine pre-rendered static build: 27 pages of server-rendered HTML, no Mintlify account required.The trade worth naming: exporting means giving up Mintlify's hosted search, analytics and AI chat, which are server-side. If you want those, connect the repo in the Mintlify dashboard and point the CNAME there instead — same hostname, different host. This PR does not force that decision; it just makes the export path a single command.
Validated with
just --list. Nothing deploys automatically.