Putting your AI-built website online

Claude or ChatGPT

A Claude artifact is a single HTML file. Copy the whole thing, paste it on our upload page, and your site is online. Nothing else needed.

Works for loose HTML from ChatGPT or any other tool too. Multiple files? Zip them and upload the zip.

Claude Code, Codex or Cursor

These tools have a terminal. Just ask them to publish your site to Dorelli, or run it yourself in your project folder:

npx github:elsaviour/dorelli-cli deploy dist --email [email protected]

The last line of the output is your address. Run it again later in the same folder and you update the same site — the key lives in .dorelli.json (keep it out of version control). No build folder? Leave out 'dist' to publish the current folder.

As an MCP tool

Rather have your AI call publishing itself, without a terminal? Add us as an MCP server. In Claude Code that is one line; other MCP clients point at the same command:

claude mcp add dorelli -- npx -y github:elsaviour/dorelli-cli mcp

Your AI then gets two tools: deploy_site (directory, email, desired name) and site_status (directory). Same .dorelli.json as the terminal variant.

Lovable

Lovable has no button to publish to another host; the way out is GitHub. Connect your project to GitHub (top right in Lovable), then add this file to your repo as .github/workflows/dorelli.yml:

name: Publish to Dorelli
on:
  push:
    branches: [main]

jobs:
  publish:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 22
      - run: npm ci && npm run build
      - run: npx github:elsaviour/dorelli-cli deploy dist --email [email protected] --yes

From then on every change in Lovable publishes itself. Your project is built on GitHub's servers, not ours — which keeps it fast and safe. After the first run the summary tells you which secrets to set so the next push updates the same site.

v0, Bolt or any project with a build step

Same idea: build your project and publish the output folder. Usually that is dist, build or out.

npm run build
npx github:elsaviour/dorelli-cli deploy dist --email [email protected]

Does your project have a server and a database? That is the App plan

Logins, orders, a dashboard with data: then your project is a Node or Next app, not a static site. It runs with us in its own container with its own Postgres database (€ 15 a month after a 14-day trial). The image is built on GitHub, never on our server, so this always goes through a workflow in your repo:

name: Deploy app to Dorelli
on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: elsaviour/dorelli-cli/.github/actions/dorelli-deploy@v1
        with:
          plan: app
          email: [email protected]
          site-id: ${{ secrets.DORELLI_SITE_ID }}
          deploy-token: ${{ secrets.DORELLI_DEPLOY_TOKEN }}
          registry-user: ${{ secrets.DORELLI_REGISTRY_USER }}
          registry-password: ${{ secrets.DORELLI_REGISTRY_PASSWORD }}

The first run creates the site and a registry token and tells you which four secrets to set. Your app gets DATABASE_URL and PORT (default 3000) as environment variables; no Dockerfile needed, we then use npm ci, npm run build, npm start. The app scales to zero without traffic — the first visit after that takes 10 to 30 seconds. Logs, restart and variables are in your portal.