Hosting and Deployment

Hosting and deployment

Docuna generates static output, so you can deploy it to any modern static hosting provider. This guide walks through the general steps — they apply to Netlify, Vercel, Cloudflare Pages, and similar platforms.

1. Push your project to GitHub

First, create a GitHub account if you do not have one, then create a new repository for your project.

From your local project folder, push your code to the repository. If you are new to Git, GitHub’s documentation covers the basic commands:

git init
git add .
git commit -m "Initial commit"
git branch -M main
git remote add origin https://github.com/your-username/your-repo.git
git push -u origin main

Once your project is on GitHub, you can connect it to a hosting provider.

2. Create an account on a modern host

Register on a static hosting provider. Common choices include:

• Netlify — simple setup, good defaults for Astro projects
• Vercel — tight integration with modern frameworks
• Cloudflare Pages — fast global network, generous free tier

Sign up using your GitHub account so the provider can access your repositories.

3. Connect your repository

After registering, create a new project on the hosting provider. Choose the option to import from GitHub, then select the repository that contains your Docuna project.

Most providers detect Astro automatically and apply the correct build settings:

• Build command: npm run build
• Output directory: dist

If your provider does not detect these, you can set them manually.

4. Deploy

Click Deploy and wait for the build to finish. The provider will install dependencies, build your site, and publish it to a temporary URL.

Every time you push a new commit to your repository, the provider will rebuild and redeploy your site automatically.

5. Connect your custom domain

To use your own domain, go to your hosting provider’s domain settings and add your domain.

You have two options:

Option A — Use the provider’s nameservers. Change your domain’s nameservers at your registrar to the ones provided by Netlify, Vercel, or Cloudflare. This is the simplest option and lets the provider manage DNS for you.

Option B — Add DNS records manually. Keep your existing nameservers and add the records (A, CNAME) that your provider specifies. This is useful if you already manage DNS elsewhere.

After the DNS changes propagate — usually within a few hours — your custom domain will point to your deployed site. The provider will also issue an SSL certificate automatically.

Notes

• Push to GitHub first. Every host listed above builds from a Git repository.
• If your build fails, check the provider’s build logs for errors.
• Most providers offer a free tier that is more than enough for a documentation site.
• Each provider has its own documentation for custom domains. Follow theirs if the steps above differ slightly.