Hosting on other providers

Every Devmachinist project is a standard Vite + React app, so besides publishing on Devmachinist you can host it anywhere that serves static files — and put it on your own domain.

1. Get the code out #

• Git (recommended): in the builder open More → Git, commit, add a remote (for example a new empty GitHub repository) and Push. Most hosts then build and redeploy automatically on every push.
• Build it yourself: clone the repository on your computer and run npm install && npm run build. The finished site is in dist/.

2. Build settings (the same everywhere) #

Pages use hash links (/#/about), so no redirect or rewrite rules are needed — any static host works.

3. Keep your data and sign-in working #

If the project uses the API builder (data, sign-in, checkout), tell the site where the API lives. Add this line inside <head> in index.html, before the main script:

<script>window.__PB_API_ORIGIN__ = 'https://devmachinist.com'</script>

Your data stays on Devmachinist and the API accepts requests from any domain. For stores, set Store URL in API → Payments to your new address so Stripe sends shoppers back to the right site.

Cloudflare Pages #

1. In the Cloudflare dashboard: Workers & Pages → Create → Pages → Connect to Git and pick your repository.
2. Framework preset Vite (or enter the build settings above). Save and deploy.
3. Custom domains → Set up a domain. If your domain's DNS is on Cloudflare, it's configured for you; otherwise add the CNAME it shows.

No Git? Upload assets and drag in your dist folder.

Vercel #

1. Add New → Project, import your Git repository.
2. Vercel detects Vite; confirm build npm run build and output dist. Deploy.
3. Settings → Domains → Add. Point your domain with the A record (76.76.21.21) or CNAME (cname.vercel-dns.com) Vercel shows.

Netlify #

1. Add new site → Import an existing project, choose your repository.
2. Build command npm run build, publish directory dist. Deploy.
3. Domain management → Add a domain and follow the DNS instructions.

Or drag the dist folder onto Sites → Deploy manually.

GitHub Pages #

1. In the repository: Settings → Pages → Source: GitHub Actions, and choose the Static HTML workflow, or add a workflow that runs npm ci && npm run build and uploads dist.
2. If the site lives at username.github.io/repo/, open vite.config.js in the project and set base: '/repo/' (not needed with a custom domain).
3. Add your domain under Settings → Pages → Custom domain.

GoDaddy #

GoDaddy can host the files or just point your domain at another host.

Point a GoDaddy domain at Cloudflare, Vercel or Netlify (recommended): in GoDaddy open My Products → your domain → DNS and add the record your host gives you — usually an A record for @ and a CNAME for www. Changes take minutes to a few hours.

Host on GoDaddy Web Hosting (cPanel):

1. Build the site (npm run build).
2. In cPanel open File Manager → public_html (delete the placeholder index.html).
3. Upload everything inside dist/ (not the folder itself), or upload a zip and Extract.
4. Turn on HTTPS under SSL/TLS Status (free with most plans).

Repeat steps 1–3 to update the site.

Your own server (VPS) #

Any Linux server with a web server works. With Caddy (automatic HTTPS):

# on your computer
npm run build && rsync -av --delete dist/ user@your-server:/var/www/my-site/

# /etc/caddy/Caddyfile on the server
example.com {
  root * /var/www/my-site
  file_server
  encode gzip
}

Then sudo systemctl reload caddy. With nginx, point root at the same folder in a server block and add a certificate with certbot --nginx.

Point your domain at the server with an A record for @ (and www) set to its IP address.

Updating #

With Git, keep working in Devmachinist and Push — Cloudflare, Vercel, Netlify and GitHub Pages rebuild automatically. For uploads (GoDaddy, VPS) build and upload again.