Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.nometria.com/llms.txt

Use this file to discover all available pages before exploring further.

This page explains what a typical day looks like when you’re actively building in an AI vibe coder with Nometria’s two-way sync enabled.

​
Setup checklist

Before following this workflow, confirm:
  • Your app is deployed via Nometria
  • Two-way sync is enabled in project Settings → Sync
  • The Chrome Extension is installed and signed in
  • You’ve set auto_merge preference in .Nometria.yml (or accepted the default)

​
The typical loop

​
1. Build in your AI builder

Open your project in Base44, Lovable, Bolt, etc. and prompt away. The Chrome Extension runs silently in the background. Every time you save or the builder generates a meaningful code change, the extension:
  1. Diffs the current file tree against the last known commit
  2. If changes are found, packages them and pushes a commit to builder/latest
  3. The commit message describes what changed (e.g. builder: update UserDashboard component)
You’ll see a small notification from the extension when a commit is pushed. You can also check the Sync tab in your Nometria dashboard to see the live commit stream.

​
2. Review the staging preview

Every push to builder/latest triggers a staging preview deploy (if enabled in .Nometria.yml). The preview URL looks like: 
https://preview-<commit-sha>.nometria.com
Open it to verify the change looks correct in a real environment before it hits production.

​
3. Merge to production

When you’re happy with the builder changes: If auto_merge: true (default): Nometria automatically merges builder/latest into main — a production redeploy starts immediately. If auto_merge: false: Nometria opens a GitHub PR from builder/latest → main. Review the diff, approve, and merge. Merging triggers the redeploy.
Use auto_merge: false when your app has active developer contributions — it forces every builder change through code review before hitting production.

​
4. Developer changes flow the same way

When a developer opens a PR to main and it gets merged:
  • Nometria’s GitHub webhook fires
  • Production redeploys from the new main commit
  • The builder sees the next push land on top of the updated codebase

​
Working with branches

For larger features, you can work on a dedicated branch: 
# Developer creates a feature branch
git checkout -b feature/payment-flow

# ... makes changes, opens PR to main
# Nometria detects the PR merge and redeploys
Meanwhile, builder changes keep flowing to builder/latest. They don’t interfere with your feature branch because they’re isolated.

​
Checking sync status

Dashboard → your project → Sync shows:
  • Last commit pushed by the extension (with timestamp and diff link)
  • Current status of builder/latest vs main (ahead/behind)
  • Active preview URLs
  • Last production deploy (commit SHA, timestamp, status)

​
Pausing sync

If you want to take a break from builder changes reaching production: Settings → Sync → Pause auto-merge The extension continues committing to builder/latest, but nothing merges to main until you unpause. Useful when a developer is doing a large refactor on main that you don’t want interrupted.

​
Example .Nometria.yml configurations

Active building, ship fast: 
sync:
  auto_merge: true
  auto_deploy_on_merge: true
  preview:
    enabled: true
    ttl: 24h
Mature product, review everything: 
sync:
  auto_merge: false
  auto_deploy_on_merge: true
  preview:
    enabled: true
    ttl: 72h
  ignored_paths:
    - "docs/**"
    - "*.md"