Skip to content

docs(deployment): add DeployHQ as a Git-triggered CI/CD option #2564

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
facundofarias wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs(deployment): add DeployHQ as a Git-triggered CI/CD option #2564

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions source/docs/one-command-deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -241,6 +241,29 @@ $ hexo generate —deploy && bip deploy

After a few moments, your website will be deployed.

## DeployHQ

[DeployHQ](https://www.deployhq.com/) is a Git-based deployment service that builds your Hexo site on its build servers and transfers the generated `public/` directory to your own infrastructure over SSH/SFTP/FTP, or to S3, Azure Blob, or Rackspace Cloud Files. It supports multiple environments per project, config-file injection, atomic releases, one-click rollback, and deploy hooks. A free tier is available.

Unlike the plugin-based options above, DeployHQ runs outside the `hexo deploy` command — you push to your Git host as usual and DeployHQ handles the build and upload.

1. Sign up at [deployhq.com/signup](https://www.deployhq.com/signup) and create a new project connected to your Hexo repository on GitHub, GitLab, or Bitbucket.

2. Add a server in the project. Provide the protocol (SSH/SFTP, FTP, S3, etc.), hostname, credentials, and the web root path (for example `public_html/`).

3. In **Build Pipeline**, add the commands needed to generate the site:

```bash
npm install
npx hexo generate
```

Set the build output path to `public/` so DeployHQ uploads the generated files rather than your sources.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use DeployHQ's deployment subdirectory setting

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 👍 / 👎.


4. Trigger a deployment manually from the dashboard, or enable automatic deployments so each push to your production branch builds and ships the site.

Refer to the [DeployHQ documentation](https://www.deployhq.com/support) for advanced configuration such as config-file injection, deploy hooks, and rollbacks.

## Other Methods

All generated files are saved in the `public` folder. You can copy them to wherever you like.
Expand Down