opscrew 0.2.1 → 0.2.3

package/README.md

@@ -27,7 +27,7 @@ Where it deploys:
 - **Cloudflare, with no server, for static and server-rendered sites:** see [Host your site on Cloudflare](https://docs.opscrew.dev/cloudflare-hosting/). Free for static files.
 - **GitHub Pages, for static sites in public repositories:** see [Publish your site on GitHub Pages](https://docs.opscrew.dev/github-pages/). Free, without custom headers or commercial use.
 
-One app can have several environments, such as dev on your computer, staging on a small server and prod on the live one, and a tested image moves to prod unchanged: see [dev, staging and prod](https://docs.opscrew.dev/environments/). Deploy jobs can also run on the server itself or on your computer: see [Self-hosted runners](https://docs.opscrew.dev/runners/).
+One app can have several environments, such as dev on your computer, staging on a small server and prod on the live one, and a tested image moves to prod unchanged: see [dev, staging and prod](https://docs.opscrew.dev/environments/). Every pull request can get its own preview at its own address, on one small server of its own: see [Previews](https://docs.opscrew.dev/previews/). Deploy jobs can also run on the server itself or on your computer: see [Self-hosted runners](https://docs.opscrew.dev/runners/).
 
 DNS goes through Cloudflare, optionally. AWS, Google Cloud, Azure and Contabo come next.
 
@@ -78,9 +78,10 @@ In Claude Code, the OpsCrew plugin runs the same steps from the chat, and every
 ## After the first deploy
 
 - `npx opscrew logs` shows the app's log lines (`--follow` for new ones), and `npx opscrew status` what runs with its CPU, memory and disk. See [Your app's logs and resource figures](https://docs.opscrew.dev/logs-and-status/).
+- `npx opscrew advise` says whether the app's servers are the right size, what could cost less and what needs attention soon, and how to apply each change. See [Advice on size, cost and upkeep](https://docs.opscrew.dev/advise/).
 - A deploy or a provision failed? See [When a deploy fails, and how to recover](https://docs.opscrew.dev/when-a-deploy-fails/): what your visitors get, what OpsCrew already put back and what to do next.
 - `npx opscrew destroy` deletes the deployment's infrastructure. It asks you to type the server name first and can take a snapshot.
-- `npx opscrew retarget --to <provider>` moves a live app to another cloud provider with its data (not yet to or from your own server or a Portainer). It builds the new server next to the old one, copies the database in a short maintenance window and switches DNS. The old server is deleted only when you run `opscrew retarget --finish`.
+- `npx opscrew retarget --to <provider>` moves a live app to another cloud provider with its data (not yet to or from your own server or a Portainer). It builds the new server next to the old one, copies the database in a short maintenance window and switches DNS. The old server is deleted only when you run `opscrew retarget --finish`. See [Moving your app to another cloud provider](https://docs.opscrew.dev/retarget/).
 - No domain yet? `npx opscrew domain buy <domain>` buys one at cost after you confirm the price, through Cloudflare, Porkbun, Namecheap or GoDaddy. Already own one? `npx opscrew domain connect <domain>` moves its DNS to Cloudflare. See [Buying or connecting a domain](https://docs.opscrew.dev/domains/).
 - Several apps under one domain? See [Your domain on Cloudflare, and several apps in one zone](https://docs.opscrew.dev/cloudflare/).
 - Every guide page is listed in [the guide's index](https://docs.opscrew.dev/).