docs(guides): add Hono deployment guide - #979
Open
robinbdru wants to merge 1 commit into
Open
Conversation
✅ Review app deployedCheck how your changes look like!
|
Cover scaffolding the nodejs template, adapting the entry point to Clever Cloud's injected PORT and to graceful shutdown on restart or redeploy, creating the Node.js application, and the environment variables it needs. Use CC_NODE_DEV_DEPENDENCIES with CC_POST_BUILD_HOOK instead of re-running npm install in CC_PRE_BUILD_HOOK, avoiding a redundant second dependency install during the build phase. Register the Vale vocabulary entry, and list the guide on the guides index page, reusing the existing Node.js icon since Hono has no dedicated one in data/icons.yaml yet. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
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 does this PR do?
Adds a guide for deploying a Hono API on Clever Cloud's Node.js runtime (same structure as the SvelteKit/Nuxt guides): scaffolding, adapting
src/index.tsto the injectedPORTand to graceful shutdown, creating the app, and the required environment variables. Also lists the guide on the guides index (reusing the Node.js icon, no dedicated Hono icon yet) and addsHonoto the Vale vocabulary.🧪 Type of Change
✅ Quick Checklist
Additional testing performed
Scaffolded a project with
create-honoand deployed it to a real Clever Cloud app to check every command and code snippet, rather than write from the framework's docs alone.That test surfaced a real issue: on the default
picobuild instance,tsccouldn't finish inside its memory cap, so the deploy just kept looping instead of failing cleanly. Scaling to--build-flavor M(already in the guide) fixed it. Added a warning callout about this failure mode, but not sure it belongs in a getting-started guide vs. being noise, open to cutting it, or moving it to the Node.js runtime page instead.A second round of testing caught a redundant step: the guide originally set
CC_PRE_BUILD_HOOK="npm install && npm run build", which installs dependencies twice (once explicitly, once via Clever Cloud's own automatic install right after). Switched toCC_NODE_DEV_DEPENDENCIES=install+CC_POST_BUILD_HOOK="npm run build"instead, confirmed on a live deploy: single install pass, build time dropped from ~10s to ~5s.AI disclosure
Drafted with Claude Code. Content and commands were verified as described above, not generated from memory.
hugoandmarkdownlint-cli2pass locally.