Publishing a Lovable app (or any Vite/React) on YaDominios Cloud

Are we compatible with Lovable? Yes.

Lovable generates a Vite + React + TypeScript + Tailwind frontend and uses Supabase as the backend (database, authentication). It also syncs your project to GitHub on every change. That's exactly what YaDominios Cloud needs: a GitHub repo that publishes itself on every push.

How each part fits

• The frontend (the Vite app): runs on YaDominios Cloud as a static site. vite build produces a dist/ folder with index.html and its assets — and dist/ is one of the folders we detect.
• The backend (Supabase): stays on Supabase. Your app calls it over HTTPS from the browser with Supabase's URL and public (anon) key, just like on any host. Nothing to move.

The one technical step: a GitHub Action that runs the build

Since we don't run your build, add this workflow to the repo Lovable syncs. It builds the app and publishes dist/ to a deploy branch you connect in the dashboard:

# .github/workflows/build.yml
name: build-for-yadominios-cloud
on: { push: { branches: [main] } }
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with: { node-version: 22 }
      - run: npm ci && npm run build   # vite build → dist/
      - uses: peaceiris/actions-gh-pages@v4
        with:
          github_token: ${{ secrets.GITHUB_TOKEN }}
          publish_branch: deploy
          publish_dir: ./dist

Your Supabase keys

Vite inlines VITE_* variables into the build (they're public, client-side). Put them as repo secrets in GitHub and pass them to the build step, or leave them in a repo .env if you don't mind them being visible (Supabase's anon key is meant for the browser). Your service_role key never goes to the frontend.

Publish

1. Connect the repo at app.yadominios.com → YaDominios Cloud (choose the name and paste the repo URL; use the deploy branch).
2. Your app goes live at yourname.sitios.dev with HTTPS.
3. Every change you make in Lovable → syncs to GitHub → the Action rebuilds → your site republishes itself.

What if I want the database on YaDominios instead of Supabase?

You can, but it's a different path: you'd replace the Supabase calls with our env.DB database inside a _worker.js (see the technical guide). To get started fast, the natural setup is to keep the backend on Supabase and the frontend on YaDominios Cloud.