Skip to main content
Fimo separates a hosted preview from production. Your everyday iteration loop is local (pnpm dev); previews and production are what you reach for when you want a hosted link or to go live.

​
Local vs hosted

The local dev server is localhost only. The Fimo dashboard preview and the shareable preview URL are served by the deployed sandbox — so seeing the site in Studio or sending someone a link requires a fimo deploy.

​
Preview — fimo deploy

Plain fimo deploy is on-demand and reversible. It commits pending changes, pushes to the current environment’s branch, syncs that environment’s preview sandbox, and prints a shareable preview URL. Run it at logical breakpoints when you want a hosted preview or a link — not after every edit.
Just need the current preview URL again (to open, screenshot, or hand off)? Run fimo preview url — sub-second, no commit or push. Never redeploy just to refresh a link.
For a headless or content-only project, a project manager can turn on Disable Preview in Project Settings. Preview navigation disappears, fimo deploy syncs changes without warming Preview, and fimo preview url explains that Preview is disabled. You can enable Preview again later.

​
Production — fimo deploy --publish

--publish pushes what’s on main and flips the project live in one shot — the simple “ship it” path. It runs from main only. Use it when the user signals “go live” or “publish”; plain preview is the default the rest of the time. For a versioned, tagged release instead, use fimo publish --version <ver>, which tags main@HEAD as release/<ver> and triggers the prod swap. Reach for it when release semantics matter; otherwise fimo deploy --publish is the lighter default.

​
At a glance

A renamed default URL or custom domain only resolves after the site is published — before that it returns “Project Not Found”.

​
What’s next

Deploy & publish

The full deploy pipeline.

Environments

Per-environment previews.

Custom domains

Put your site on your own URL.