Recent changes to Remote Runners

Remote Runners modified by Viktor Fási

Viktor Fási — Wed, 06 May 2026 09:06:51 -0000

--- v2
+++ v3
@@ -1,12 +1,12 @@
 # Remote Runners

-Run tests on remote machines by deploying runners that connect back to your Lastest2 server via HTTP polling.
+Run tests on remote machines by deploying runners that connect back to your Lastest server via HTTP polling.

 ## Architecture

 ![Remote Runners Architecture](images/runner-logic.png)

-**How it works:** The Lastest2 server queues test commands into SQLite (`runner_commands` table). Remote runners poll `POST /api/ws/runner` every 3-5 seconds, claim pending commands, execute them with Playwright, and upload screenshots + results back over the same channel. Authentication uses Bearer tokens (SHA256 hashed in DB).
+**How it works:** The Lastest server queues test commands into SQLite (`runner_commands` table). Remote runners poll `POST /api/ws/runner` every 3-5 seconds, claim pending commands, execute them with Playwright, and upload screenshots + results back over the same channel. Authentication uses Bearer tokens (SHA256 hashed in DB).

 ---

@@ -21,21 +21,21 @@
     npm install -g @lastest/runner

     # Start as daemon

-    lastest2-runner start -t YOUR_TOKEN -s https://your-lastest2-server
+    lastest-runner start -t YOUR_TOKEN -s https://your-lastest-server

     # Or run in foreground

-    lastest2-runner run -t YOUR_TOKEN -s https://your-lastest2-server
+    lastest-runner run -t YOUR_TOKEN -s https://your-lastest-server

 ---

 ## Runner CLI

     :::bash

-    lastest2-runner start -t <token> -s <server-url>  # Start as background daemon
-    lastest2-runner stop                               # Stop the daemon
-    lastest2-runner status                             # Show runner status
-    lastest2-runner log [-f] [-n <lines>]              # View logs (-f to follow)
-    lastest2-runner run -t <token> -s <server-url>     # Run in foreground
+    lastest-runner start -t <token> -s <server-url>  # Start as background daemon
+    lastest-runner stop                               # Stop the daemon
+    lastest-runner status                             # Show runner status
+    lastest-runner log [-f] [-n <lines>]              # View logs (-f to follow)
+    lastest-runner run -t <token> -s <server-url>     # Run in foreground

 ---

@@ -62,7 +62,7 @@

 ## Configuration

-Runner config is stored in `~/.lastest2/`:
+Runner config is stored in `~/.lastest/`:

 - `runner.pid` -- daemon process ID
 - `runner.log` -- runner log file
 - `runner.config.json` -- saved configuration
@@ -71,7 +71,7 @@

 ## Managing Runners

-In the Lastest2 UI (Settings > Runners, admin only):
+In the Lastest UI (Settings > Runners, admin only):

 - Register new runners
 - View connected runners and their status
 - See system info (OS, CPU, memory)
</server-url></token></lines></server-url></token></server-url></token></lines></server-url></token>

Remote Runners modified by Viktor Fási

Viktor Fási — Wed, 06 May 2026 09:06:51 -0000

--- v1
+++ v2
@@ -1,6 +1,12 @@
 # Remote Runners

-Run tests on remote machines by deploying runners that connect back to your Lastest2 server via WebSocket.
+Run tests on remote machines by deploying runners that connect back to your Lastest2 server via HTTP polling.
+
+## Architecture
+
+![Remote Runners Architecture](images/runner-logic.png)
+
+**How it works:** The Lastest2 server queues test commands into SQLite (`runner_commands` table). Remote runners poll `POST /api/ws/runner` every 3-5 seconds, claim pending commands, execute them with Playwright, and upload screenshots + results back over the same channel. Authentication uses Bearer tokens (SHA256 hashed in DB).

 ---

Remote Runners modified by Viktor Fási

Viktor Fási — Wed, 06 May 2026 09:06:50 -0000

Remote Runners

Run tests on remote machines by deploying runners that connect back to your Lastest2 server via WebSocket.

Setup

Register a runner in Settings > Runners
Copy the token (shown only once)
Install and run on your target machine:

:::bash

Install from npm

npm install -g @lastest/runner

Start as daemon

lastest2-runner start -t YOUR_TOKEN -s https://your-lastest2-server

Or run in foreground

lastest2-runner run -t YOUR_TOKEN -s https://your-lastest2-server

Runner CLI

lastest2-runner start -t <token> -s <server-url>  # Start as background daemon
lastest2-runner stop                               # Stop the daemon
lastest2-runner status                             # Show runner status
lastest2-runner log [-f] [-n <lines>]              # View logs (-f to follow)
lastest2-runner run -t <token> -s <server-url>     # Run in foreground

Capabilities

Capability	Description
Run	Execute tests remotely
Record	Record new tests on remote machines
Parallel	Configurable max parallel tests per runner
System Info	Automatic OS, architecture, memory, and CPU reporting

Runner v2 Features

Concurrent multi-task support -- run multiple tests simultaneously
SHA256 code integrity verification -- ensures test code hasn't been tampered with
Remote recording -- record tests on remote machines
Heartbeat polling with command queuing -- reliable connection management
Per-test abort support -- cancel individual tests without affecting others

Configuration

Runner config is stored in ~/.lastest2/:

runner.pid -- daemon process ID
runner.log -- runner log file
runner.config.json -- saved configuration

Managing Runners

In the Lastest2 UI (Settings > Runners, admin only):

Register new runners
View connected runners and their status
See system info (OS, CPU, memory)
Configure parallel execution limits
Remove runners

Recent changes to Remote Runners

Remote Runners modified by Viktor Fási

Remote Runners modified by Viktor Fási

Remote Runners modified by Viktor Fási

Remote Runners

Setup

Install from npm

Start as daemon

Or run in foreground

Runner CLI

Capabilities

Runner v2 Features

Configuration

Managing Runners