Update

GitOrigin-RevId: 5a708dc68bf96caf48b9cdc40ffb5f6cebb4a06e

Author: ianmacartney

self-hosted/fly/README.md

@@ -110,13 +110,13 @@ Steps:
 
    ```sh
    cd <your-frontend-app-directory>
-   npm install convex
+   npm install convex@alpha
    ```
 
    To continuously deploy code for development:
 
    ```sh
-   npx convex dev
+   npx convex self-host dev
    ```
 
    This will continuously deploy your Convex functions as you edit them. It will
@@ -126,16 +126,16 @@ Steps:
    To deploy code once:
 
    ```sh
-   npx convex deploy
+   npx convex self-host deploy --env-file <path to env file>
    ```
 
    To deploy code to a different backend, you can pass the `--env-file` flag or
    set the self-hosted environment variables before calling `npx convex deploy`.
 
    **Note:** It's up to you whether a backend is for development or production.
    There is no distinction within the instance. If you only have one backend,
-   you can run `npx convex dev` or `npx convex deploy` depending on whether you
-   want it to live-update or not.
+   you can run `npx convex self-host dev` or `npx convex self-host deploy`
+   depending on whether you want it to live-update or not.
 
    An extension of this is that you can have many backends for staging or
    previews. The difference will be in the environment variables.