example.com/blog. Your website host handles the proxy configuration.
Run domain from the same publication folder after its first deployment. The CLI
uses that folder’s deployment site. No site-selection flags are required.
Connect a subfolder
example.com/resources/blog work too.
Choose Vercel, Cloudflare, or nginx. The CLI prints the proxy rules for
your existing website. Apply them using that host’s configuration and deployment
workflow, then press Enter to verify the connection. You do not need the Lettercamp
dashboard. The CLI does not sign in to your hosting provider or deploy its configuration.
The proxy forwards /blog and its descendants to your Lettercamp site while
preserving the path. Your other website routes stay with your existing host.
Keep your current DNS and HTTPS setup; DNS records cannot route individual paths.
Lettercamp checks https://example.com/blog/.well-known/lettercamp, then rebuilds
your publication with /blog as its base path. It reports success once the build
is live. Use full URLs such as https://example.com/pricing for links to the main
website; publication links such as /about point inside the subfolder.
Check or remove the connection
Runnpx lettercamp domain to check progress or resume setup. Verification waits up
to ten minutes before asking you to run it again; your setup is saved.
A site can use one custom hostname or one subfolder at a time. Run
npx lettercamp domain remove and confirm to return to the Lettercamp address.
Wait for disconnection to finish before removing your website’s proxy rules.
Remove an existing connection before adding a different address.