docs: make the guides CLI-only, drop every Console mention

Author: patrikbraborec

README.md

@@ -14,7 +14,7 @@ See `requirements/*.md` for the full behavioural spec (`system.md`, `api.md`,
 ## Documentation
 
 - [Quick start](docs/quick-start.md) - start the runtime with Apify CLI or Docker, connect the CLI,
-  push and run an Actor, view the results, and the proposed `apify local` commands.
+  push and run your Actor, view the results, and the proposed `apify local` commands.
 - [Local development workflow](docs/local-development.md) - build, run, view results, iterate without
   rebuilding, debug with your IDE, test platform events, simulate users, fall back to the platform,
   limitations, and proposed improvements.

docs/local-development.md

@@ -73,11 +73,7 @@ To use Apify Proxy from local runs, set `APIFY_PROXY_PASSWORD` on the runtime co
 
 ## View the results
 
-Everything a run produced is available in three places.
-
-### Console
-
-Open [http://localhost:3000](http://localhost:3000). The Console lists Actors, builds, runs, logs, and storages. A run's detail page links to its default storages, and log views render ANSI colours. The Console accepts the URL shapes Apify CLI prints for the Apify Console, so links in `apify call` output open the right page.
+Everything a run produced is available in two places.
 
 ### CLI
 
@@ -117,7 +113,7 @@ For Actors with a slow build, such as browser images or heavy Python installs, t
     apify call --input '{"maxPages": 3}'
     ```
 
-To clear the registration, submit an empty body: `--body '""'`. The same field is on the Actor's page in the Console.
+To clear the registration, submit an empty body: `--body '""'`.
 
 **How the mount behaves**
 
@@ -160,13 +156,13 @@ apify api POST /actor-runtime/debug/<actorId> --body '{"enabled": false}'
 
 The platform stops, migrates, and aborts Actors. You can trigger these events against a `RUNNING` run to check that your Actor persists its state and resumes correctly.
 
-| Event          | How to trigger                                                                                       | What the Actor sees                                                                                                                                                                                                  |
-| -------------- | ---------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Migration      | `apify api POST /actor-runtime/migrate/<runId>`, or the **Migrate** button on the run's Console page | A `migrating` event, then its container stops about five seconds later and a new container starts for the same run with the same id, environment, and storages. In-memory state is gone. The status stays `RUNNING`. |
-| Reboot         | `apify api POST v2/actor-runs/<runId>/reboot`                                                        | An immediate stop and restart with no warning event. The SDKs call this from their default migration handler.                                                                                                        |
-| Graceful abort | `apify api POST 'v2/actor-runs/<runId>/abort?gracefully=true'`                                       | `aborting` and `persistState` events, then the container stops 30 seconds later.                                                                                                                                     |
-| Abort          | `apify api POST v2/actor-runs/<runId>/abort`                                                         | The container stops at once.                                                                                                                                                                                         |
-| Timeout        | `apify call --timeout 10`                                                                            | The run ends as `TIMED-OUT` when the deadline passes. The budget is per run, so a migrated run gets only the remaining time.                                                                                         |
+| Event          | How to trigger                                                 | What the Actor sees                                                                                                                                                                                                  |
+| -------------- | -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Migration      | `apify api POST /actor-runtime/migrate/<runId>`                | A `migrating` event, then its container stops about five seconds later and a new container starts for the same run with the same id, environment, and storages. In-memory state is gone. The status stays `RUNNING`. |
+| Reboot         | `apify api POST v2/actor-runs/<runId>/reboot`                  | An immediate stop and restart with no warning event. The SDKs call this from their default migration handler.                                                                                                        |
+| Graceful abort | `apify api POST 'v2/actor-runs/<runId>/abort?gracefully=true'` | `aborting` and `persistState` events, then the container stops 30 seconds later.                                                                                                                                     |
+| Abort          | `apify api POST v2/actor-runs/<runId>/abort`                   | The container stops at once.                                                                                                                                                                                         |
+| Timeout        | `apify call --timeout 10`                                      | The run ends as `TIMED-OUT` when the deadline passes. The budget is per run, so a migrated run gets only the remaining time.                                                                                         |
 
 The run log is cumulative across restarts, with a marker line between container incarnations.
 
@@ -178,8 +174,6 @@ Each distinct token gets its own user, and API responses are scoped to that user
 apify api v2/datasets -H '{"authorization": "Bearer another-token"}'
 ```
 
-The Console has no login and shows every user's objects with their owner, which helps you verify that scoping works.
-
 ## Fall back to the Apify platform
 
 If a call fails because the runtime does not have that Actor, run, or storage id, or does not implement the endpoint, you can have such calls relayed to the Apify platform:
@@ -189,7 +183,7 @@ apify api POST /actor-runtime/api-fallback --body '{"fallbackUnimplementedEnable
 apify api GET /actor-runtime/api-fallback
 ```
 
-Both toggles are off by default and reset on every restart. The same toggles are on the Console's Settings page. Relayed responses carry the `x-actor-runtime-fallback` and `x-actor-runtime-fallback-trigger` headers so you can tell where an answer came from.
+Both toggles are off by default and reset on every restart. Relayed responses carry the `x-actor-runtime-fallback` and `x-actor-runtime-fallback-trigger` headers so you can tell where an answer came from.
 
 **Use a token you trust with real writes**
 
@@ -210,13 +204,13 @@ The runtime is a development tool for one developer: fewer than ten Actors, five
 - **Not implemented:** Actor tasks, schedules, webhooks, and most of the API outside Actors, builds, runs, logs, and the three storage types. Unknown endpoints return `404` unless [fallback](#fall-back-to-the-apify-platform) is on.
 - **Request queues:** locks do not expire, so `head/lock` hands a request out until an explicit unlock, reclaim, or runtime restart. Request deletion returns `501`. `GET /requests` lists only requests this runtime process has seen and ignores filters. Counts on the queue object are authoritative.
 - **Storage metadata:** `hadMultipleClients` is always `false`, `stats` fields are zero, and dataset item options such as `fields` or `clean` apply after paging, so `total` counts unfiltered items.
-- **Users:** any non-empty token is accepted. There is no real authentication, and the Console shows every user's objects.
+- **Users:** any non-empty token is accepted. There is no real authentication.
 - **One runtime per data directory.** Do not start two runtimes on the same `data` directory.
 - **Operating systems:** Linux is tested. macOS works with the networking note in the [quick start](quick-start.md#start-with-docker). Windows with Docker Desktop and WSL 2 is untested.
 
 ## Next steps
 
-- Read the exact behaviour in `requirements/api.md`, `requirements/actor-driver.md`, `requirements/storage.md`, and `requirements/console.md`.
+- Read the exact behaviour in `requirements/api.md`, `requirements/actor-driver.md`, and `requirements/storage.md`.
 - When your Actor works locally, unset the environment variables and `apify push` to deploy it to the Apify platform.
 
 ## Proposed improvements

docs/quick-start.md

@@ -52,7 +52,7 @@ Add `-d` to run the container in the background. Stop it with `docker stop actor
 
 **Docker Desktop on macOS**
 
-On some Docker Desktop installations, `localhost:3333` and `localhost:3000` time out even though the runtime is healthy. The runtime joins a second Docker network, `apify-local`, so Actor containers can reach it, and Docker Desktop then routes replies through the wrong network. Start the container on that network directly so it has only one:
+On some Docker Desktop installations, requests to the runtime's ports time out even though the runtime is healthy. The runtime joins a second Docker network, `apify-local`, so Actor containers can reach it, and Docker Desktop then routes replies through the wrong network. Start the container on that network directly so it has only one:
 
 ```
 docker network create apify-local 2>/dev/null || true
@@ -74,7 +74,7 @@ To verify that the runtime is up, run:
 apify local status
 ```
 
-The command reports the API at `http://localhost:3333`, the Console at `http://localhost:3000`, and the data directory, and exits non-zero when the runtime is down.
+The command reports the runtime API URL, `http://localhost:3333`, and the data directory, and exits non-zero when the runtime is down.
 
 **Proposed command**
 
@@ -84,7 +84,7 @@ The command reports the API at `http://localhost:3333`, the Console at `http://l
 APIFY_CLIENT_BASE_URL=http://localhost:3333 apify api v2/users/me
 ```
 
-It prints your user as JSON when the runtime is up, and a connection error when it is not. You can also open [http://localhost:3000](http://localhost:3000) in your browser.
+It prints your user as JSON when the runtime is up, and a connection error when it is not.
 
 ## 2. Connect Apify CLI
 
@@ -141,19 +141,22 @@ Create one with [`apify create`](https://docs.apify.com/cli/docs/quick-start), o
 
 ## 4. View the results
 
-Open [http://localhost:3000](http://localhost:3000) to browse the Actor, its builds and runs, logs, and the dataset, key-value store, and request queue the run produced.
+To list the runs of your Actor, run:
 
-You can also use the CLI:
+```
+apify runs ls
+```
+
+To read what a run produced, use the ids `apify call` printed:
 
-| Command                                                  | Shows                                   |
-| -------------------------------------------------------- | --------------------------------------- |
-| `apify runs ls`                                          | Runs of the Actor in the current folder |
-| `apify datasets info <datasetId>`                        | Dataset metadata, including item count  |
-| `apify api v2/datasets/<datasetId>/items`                | Dataset items                           |
-| `apify api v2/key-value-stores/<storeId>/records/OUTPUT` | One key-value store record              |
-| `apify api v2/actor-runs/<runId>/log`                    | The run log                             |
+| Command                                                  | Shows                                  |
+| -------------------------------------------------------- | -------------------------------------- |
+| `apify datasets info <datasetId>`                        | Dataset metadata, including item count |
+| `apify api v2/datasets/<datasetId>/items`                | Dataset items                          |
+| `apify api v2/key-value-stores/<storeId>/records/OUTPUT` | One key-value store record             |
+| `apify api v2/actor-runs/<runId>/log`                    | The run log                            |
 
-`apify api` sends any request to the runtime API, so everything the Console shows is available this way. The raw files are in the `data` directory. Read them freely, but change state through the API.
+`apify api` sends any request to the runtime API, so every Actor, build, run, log, and storage is available this way. The raw files are in the `data` directory. Read them freely, but change state through the API.
 
 ## 5. Stop and reset the runtime