Add Hostinger to deployment documentation

[agneliutkiene]

Request

I'd like to add Hostinger to the deployment documentation to help VitePress users deploy their sites with managed hosting.

Motivation

About Hostinger:
Hostinger is a web hosting platform with managed Node.js hosting that supports VitePress sites. We serve 1M+ developers worldwide and provide simple deployment for static site generators and Node.js applications.

Why add this:

• VitePress users need more deployment options
• Hostinger provides zero-config deployment with auto-detection
• Simple, affordable managed hosting solution
• Includes SSL, CDN, and DDoS protection by default

Proposed Solution

Add a new deployment guide page covering:

Key features for VitePress users:

• Native framework auto-detection (VitePress recognized automatically)
• One-click GitHub deployment with automatic rebuilds
• Direct file upload option (ZIP)
• Managed infrastructure with SSL, CDN, DDoS protection
• Predictable pricing from $2.99/mo (no usage-based billing)
• Global CDN for fast content delivery
• 24/7 developer support

What I'll provide:

• Complete deployment guide following VitePress docs style
• Step-by-step instructions for both GitHub integration and file upload
• Configuration examples (base paths, environment variables)
• Troubleshooting section
• Screenshots (if helpful)

Additional Context

• Hostinger already supports VitePress deployments (tested and working)
• The platform auto-detects VitePress and configures builds automatically
• Deployment takes minutes with zero DevOps required
• Free domain and business email included for 1 year

I'm ready to contribute this documentation and will follow VitePress contribution guidelines including:

• Following commit message conventions
• Checking out from main branch
• Testing locally with pnpm run docs
• Keeping the PR focused

Would the maintainers be open to this addition?

[psarin]

I'm not a maintainer but this would be quite helpful to me!

[brc-dd]

Thanks. But since you work at Hostinger, won't it make sense to write developer docs/tutorials on your own site? I see that you've created similar issues/discussions across multiple framework repos. I think it might be better to creates guides on Hostinger's official site itself and we can link it back similar to how we do it for other hosting providers:

You can also just publish a generic how to deploy static websites (from GitHub) to Hostinger, not necessarily specific for VitePress. Maybe like https://www.hostinger.com/support/how-to-upload-a-static-front-end-application-on-agency-plan/? If there is any config specific to VitePress we can keep here, but having troubleshooting guide and screenshots here will be off-topic.

[agneliutkiene]

Hey!

Fair point 👍 We do have a deployment guide on our side (https://www.hostinger.com/support/how-to-deploy-a-nodejs-website-in-hostinger/). The reason for approaching here is mainly discoverability. Vite is currently the #1 most deployed framework on our platform, and devs often look for quick, framework-specific guidance directly in your ecosystem. The idea isn’t to duplicate full docs, but to keep things lightweight on your side and link back to our official guide for the full flow, screenshots, and troubleshooting.

[brc-dd]

Thanks. I think we can add that URL and write some small description maybe like -

You can deploy your VitePress project with Hostinger by following these instructions. While configuring build settings choose VitePress as the framework and adjust the root directory to ./docs.

I'm trying to avoid longer descriptions because it will be hard for us to maintain and keep them up to date for all hosting providers.

PS: didn't Hostinger used to allow just uploading the static files? That can also be mentioned if it's still there. People can build their apps locally and upload docs/.vitepress/dist from Hostinger's UI.

^ Also, not sure if that root directory configuration is needed, check once maybe 🤷‍♂️

[agneliutkiene]

Thanks, yes, your suggested description would work 🙇

> Didn't Hostinger used to allow just uploading the static files?

Not anymore. We're now supporting Node.js websites and their builds directly from the GitHub repositories or .ZIP files. We're performing required build commands (depending on the detected) framework and we also handle all required packages installation during the deployment stage as well. So users themselves do not require to any dependencies installs or package manager installs via SSH.

Also, not sure if that root directory configuration is needed, check once maybe

Based on the Framework users are using we're automatically detecting default root directory, if user didn't set it to any custom value, we'll be taking the default values. However, during the deployment of the app, user can change it freely as well.

[agneliutkiene]

Hey! I've submitted a commit. When is it going to be confirmed? :)

[brc-dd]

Ah, you need to create a pull request for that commit.

[agneliutkiene]

I see, thank you! I'm a new GitHub user :)