weroost

Create and publish fast marketing sites (landing pages) from your terminal.

weroost is the command-line client for Weroost — a hosted platform that builds and serves your sites for you. You edit plain Astro sources locally; the server does the build, hosting, TLS and custom domains. It works out of the box: install, run weroost init, and you are publishing to the hosted Weroost service with zero configuration — no server to set up, no tokens to paste.

npm install -g weroost
weroost init

init is the one-shot setup: it creates (or logs into) your account on the hosted service, installs the Claude Code skill into the current folder, and optionally connects a GitHub repo for your sites (OAuth device flow — no manual tokens). Then:

weroost create my-project/my-site    # scaffold ./my-project/my-site/
weroost preview my-project/my-site   # live preview while you iterate
weroost push my-project/my-site      # upload, build, get the live URL

preview uploads your sources and opens a preview URL that always serves the latest upload — the published site stays untouched. push publishes: it waits for the build and prints the live URL. You never run a build locally; the Weroost server does it.

Why weroost

• Zero infrastructure. No hosting, no CI, no astro build on your machine. The hosted service builds and serves every site.
• Everything from the terminal. Registration, publishing, custom domains, DNS checks and analytics are all commands — the web admin is optional.
• Instant preview. weroost preview gives a shareable URL for the current draft without touching what is live.
• AI-native. weroost skill teaches Claude Code your site structure and publish flow, so "create a landing for X and publish it" just works.

Commands

weroost init                      one-shot setup: account + skill + GitHub repo

weroost register                  create an account, get an API token
weroost login                     log in to an existing account
weroost whoami                    current account and host

weroost create <project>/<site>   scaffold a new site
weroost preview [dir]             upload sources and open a live preview
weroost push [dir]                upload sources and publish
weroost publish <project>/<site>  rebuild from the source without uploading
weroost sites                     list sites, statuses and domains
weroost open [dir]                open the published site

weroost github [owner/repo]       create/connect a GitHub repo (OAuth device flow)
weroost scan                      re-import projects/sites from the source
weroost domain <project> <domain> attach a custom domain (--clear to remove)
weroost dns <hostname>            verify DNS points to the server
weroost analytics <project> <id>  set a Yandex Metrika counter

weroost connect <url>             point the CLI at a self-hosted weroost server
weroost host list|add|use|rm      manage weroost servers
weroost skill                     install the Claude Code skill

Self-hosting (optional)

By default every command talks to the hosted Weroost service — you do not need to configure anything. If you run your own Weroost server, the CLI works with any number of them (self-hosted included). Each server exposes its own installer that installs the CLI and points it at that server:

curl -fsSL https://admin.your-domain.com/install.sh | sh    # macOS / Linux
irm https://admin.your-domain.com/install.ps1 | iex         # Windows PowerShell

Or wire it manually:

weroost connect https://admin.lab.example.com   # add + make default
weroost register                                # account on that server
weroost push my-project/my-site --host lab.example.com
weroost host list                               # see all servers, switch with host use

Credentials are stored per server in ~/.config/weroost/config.json — you stay logged in to all of them at once, and the hosted weroost host is always available without setup.

Claude Code

weroost skill installs a skill into ./.claude/skills/weroost so Claude Code knows the site structure, the built-in components and the publish workflow — ask it to "create a landing for X and publish it" and it will.