docs(deployment): add DeployHQ as a Git-triggered CI/CD option#2564
docs(deployment): add DeployHQ as a Git-triggered CI/CD option#2564facundofarias wants to merge 1 commit into
Conversation
|
✅ Theme thumbnails validation completed. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 967ac44a1e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| npx hexo generate | ||
| ``` | ||
|
|
||
| Set the build output path to `public/` so DeployHQ uploads the generated files rather than your sources. |
There was a problem hiding this comment.
For DeployHQ builds, the setting that limits uploads to Hexo's generated files is the server/repository Deployment Subdirectory, not a build output path; DeployHQ's Hexo guide says to set Deployment Subdirectory to public so only the compiled site is transferred. As written, users may look for the wrong Build Pipeline field or leave the deployment subdirectory unset, which causes DeployHQ's first deployment to upload the whole repository instead of just public/.
Useful? React with 👍 / 👎.
1 participant
This PR adds DeployHQ to the One-Command Deployment guide as an additional Git-triggered CI/CD option, alongside the existing Netlify, Vercel, and Bip entries. DeployHQ builds Hexo sites in its own build pipeline (
npm install && hexo generate) and ships the generatedpublic/directory to user-owned infrastructure over SSH/SFTP/FTP or to S3/Azure Blob/Rackspace Cloud Files, which fills a gap for Hexo users who want push-to-deploy onto a VPS or shared host without writing their own rsync/SFTP credentials into_config.yml.The section follows the structure of the existing Netlify and Vercel entries (short intro + numbered setup steps) and does not require a new
hexo-deployer-*plugin because DeployHQ runs outside thehexo deploycommand. English-only for this PR; happy to coordinate with translators on follow-up PRs.