site_publish

com.gemmein/mcp · Verify this server

Publishes a site draft to the Development site (https://<slug>-dev.gemmein.dev): the draft's files over the ones it serves now, minus the paths in remove (replace: true = the draft's files alone). Gemmein scans every text file for a secret key, checks the limits, uploads only the files that changed, makes it the version the Development address serves (replacing the one it served), then opens the address and waits for it to answer the new version. The answer is PUBLISHED (env, the address and the version) or FAILED (the step — build, upload, size, secret_scan or address_check — the file and line when known, the reason and the fix). The Development site is a private preview: only the founder, signed in to Gemmein, plus anyone holding a 7-day share link can open it; 30 days idle unpublishes it (its files are kept; publishing again restores it). An open preview tab reloads itself within seconds of a publish. The public Live site changes only by site_promote, which the founder approves. Each publish is on the founder's Logs; Development caps how many publishes a day. This is what a founder may call updating the website or changing the page.