Skip to content

docs: add hostinger as node.js hosting provider - #2194

Merged
atinux merged 3 commits into
nuxt:mainfrom
ArnasDon:docs/add-hostinger-deployment
Mar 5, 2026
Merged

docs: add hostinger as node.js hosting provider#2194
atinux merged 3 commits into
nuxt:mainfrom
ArnasDon:docs/add-hostinger-deployment

Conversation

@ArnasDon

@ArnasDon ArnasDon commented Mar 3, 2026

Copy link
Copy Markdown
Contributor

🔗 Linked issue

As far as I've seen, there are no such issues to add Hostinger into documentation.

📚 Description

Hi, adding Hostinger into documentation as one of the Node.js Hosting providers. We do support Nuxt.js deployment via GitHub integration or by simply uploading the files. We already have some nuxt.js deployments on our hosting and want to inform other users of such possibility.

ArnasDon added 2 commits March 3, 2026 18:57
Include Hostinger as an additional Hosting provider where clients can deploy their Nuxt application.
@ArnasDon
ArnasDon requested a review from atinux as a code owner March 3, 2026 17:03
@vercel

vercel Bot commented Mar 3, 2026

Copy link
Copy Markdown
Contributor

@ArnasDon is attempting to deploy a commit to the Nuxt Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Mar 3, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

A new Markdown documentation file for Hostinger deployment was added to the content/deploy directory. The file includes front-matter metadata (title, description, component image, logo source, category, Nitro preset, and website link) and outlines two deployment approaches: Git-based deployment via GitHub repository connection with automatic build detection and redeployment, and manual deployment via file upload through Node.js Apps. The file concludes with a reference link to additional Node.js deployment resources.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description check ✅ Passed The description is directly related to the changeset, explaining the purpose of adding Hostinger documentation and its deployment methods.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check ✅ Passed The PR title accurately describes the main change: adding Hostinger as a Node.js hosting provider to the documentation.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@content/deploy/hostinger.md`:
- Around line 23-27: There's a numbering typo in the ordered list where the item
labeled "7." follows steps "1.–3."; update the list item currently numbered "7."
to "4." so the sequence reads 1., 2., 3., 4., and keep the rest of the steps'
formatting consistent in the hostinger.md content.

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 330472b and 9851baf.

⛔ Files ignored due to path filters (1)
  • public/assets/integrations/hostinger.svg is excluded by !**/*.svg
📒 Files selected for processing (1)
  • content/deploy/hostinger.md

Comment thread content/deploy/hostinger.md
@vercel

vercel Bot commented Mar 4, 2026

Copy link
Copy Markdown
Contributor

Deployment failed with the following error:

The provided GitHub repository does not contain the requested branch or commit reference. Please ensure the repository is not empty.

@ArnasDon ArnasDon left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Fixed a typo within numeration.

@atinux atinux changed the title Docs/add hostinger deployment option as one of the providers docs: add hostinger as node.js hosting provider Mar 4, 2026
@atinux atinux changed the title Docs/add hostinger deployment option as one of the providers docs: add hostinger as node.js hosting provider Mar 4, 2026
@atinux
atinux merged commit 44cda49 into nuxt:main Mar 5, 2026
6 of 7 checks passed
facundofarias added a commit to facundofarias/nuxt.com that referenced this pull request Jun 7, 2026
Add a new per-provider page under content/deploy/ documenting how
to deploy a Nuxt application to your own server with DeployHQ.

DeployHQ is a Git-based deployment automation platform: it connects
to a GitHub/GitLab/Bitbucket repository, runs the Nuxt build on its
build pipeline servers, and transfers the .output/ directory to a
user-controlled server over SSH/SFTP/FTP (or to S3, Azure Blob, or
Rackspace Cloud Files). The page uses the standard Nitro node-server
preset, mirroring the precedent set by content/deploy/hostinger.md
(PR nuxt#2194).

Also adds the DeployHQ logo SVG at public/assets/integrations/deployhq.svg.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants