07 · Publish

Generate the production build. It's your compile test: if Vite bundles the app without errors, the code is sound enough to publish.

npm run build

Real output:

vite v5.4.21 building for production...
✓ 34 modules transformed.
dist/index.html                   0.40 kB │ gzip:  0.27 kB
dist/assets/index-tn0RQdqM.css    0.00 kB │ gzip:  0.02 kB
dist/assets/index-BERJrSU-.js   143.00 kB │ gzip: 46.00 kB
✓ built in 274ms

The result is a dist/ folder ready to serve. Next, run doctor to validate the manifest one last time:

fayz doctor

⚠ plugins referenced by manifest are resolved by the platform bundle, not public npm packages: dashboard

0 error(s), 1 warning(s)

Your app is your repository. Before committing, add the .fayz/ folder to .gitignore — it holds the local deploy link (.fayz/project.json) and shouldn't go into the repository. The scaffold doesn't cover this yet, so do it manually:

# at the app root, make sure .fayz/ is ignored
echo ".fayz/" >> .gitignore

Now initialize the repository and make the first commit:

git init
git add .
git commit -m "feat: my Fayz app"

Create the remote repository — via the GitHub CLI or the website — and push:

# with the gh CLI
gh repo create my-store --private --source=. --push

# or, if you created the repo on the website:
git remote add origin https://github.com/<your-user>/my-store.git
git push -u origin main

Deploying needs an access token. Generate one under Fayz → Settings → Access tokens — it comes with the fayz_ prefix. (Deploy access is rolling out to the invited developer network.)

fayz login

Paste the token when prompted. Real output:

✓ Token salvo em ~/.fayz/credentials.json (permissão 0600).
  fayz_xxx…xxx
  O token será validado no primeiro deploy (nenhuma chamada de rede foi feita agora).

Login is local: it only writes the token with 0600 permissions and validates it later, on the first deploy. Useful commands:

fayz login --status   # shows the masked token, if there is one
fayz logout           # removes credentials.json

On CI or ephemeral machines, use the FAYZ_TOKEN environment variable instead of fayz login — the CLI reads it directly.

Before uploading for real, run the dry run. It lists exactly what would be sent and where it would go, with no network calls at all:

fayz deploy --dry-run

Real output:

▸ Arquivos a enviar de my-store:
  app.manifest.json  (1087 B)
  index.html  (299 B)
  …
  Total: 13 arquivo(s), 7099 B.
  Destino: novo projeto 'my-store' (será criado no primeiro deploy)
  (dry-run — nenhuma chamada de rede foi feita)

The project name is derived from the name field in your package.json. Check the list and the destination before going further.

Now upload for real:

fayz deploy

The CLI confirms the destination before acting (use --yes to skip the confirmation; in a non-interactive shell it fails fast instead of acting on its own). On the first deploy it creates the project on the platform and writes .fayz/project.json with { projectId, name }; on subsequent deploys it reuses that file, shipping to the same project. The code uploads in batches, the platform builds on the server (install + Vite) and returns the final URL:

🔗 https://my-store.live.fayz.ai