Skip to main content

Try Service Lasso

Bring up the demo, open the browser UI, and try managing a service. For background, see the introduction.

1. Start the demo​

Install Node.js 22+, npm, and Git. You also need internet access to download the service releases; the first start takes longer than subsequent starts. Service artifacts have platform-specific support; for example, the pinned Python provider is Windows-only and is skipped on other hosts.

Run these commands in PowerShell or your usual terminal:

git clone --branch develop https://github.com/service-lasso/service-lasso.git
cd service-lasso
npm ci
npm run demo

The demo command builds the runtime, uses the checked-in services/ manifests, and keeps its runtime state in workspace/demo-instance/. Keep the terminal open while trying it.

2. Open Service Admin​

Open http://127.0.0.1:17700/.

A fresh workspace may show first-run setup. Complete the setup and save the credentials and recovery information it provides. Regular services wait until setup is complete. If setup has finished but a service remains stopped, use its Install/Configure/Start actions in Admin when offered. The independent example review records a current Windows recycle/shutdown defect; recycle is not a qualified recovery step. For setup details, see vault bootstrap.

3. Try a service​

On the first-run credential screen, use both copy buttons, save both values privately, tick I saved this token, and continue. Sign in using the saved credential or the offered local session.

Once the services are running:

  1. Open the Echo demo to see a managed service respond.
  2. Find echo-service in Service Admin, open Details, and inspect its status and logs.
  3. On that detail page, click Stop service, accept its confirmation dialog, wait for Stopped, then click Start service and reload the Echo page.

Use the detail-page controls: the evaluated Admin release's table-row Stop button rejects the action because it does not present the required confirmation.

The demo includes a browser admin, Echo Service, NGINX, Traefik, and supporting providers. See baseline services for their roles and platform notes.

Automatic service startup​

Normal runtime launches start enabled services automatically after the runtime API is ready. This is the default for both npm start and the demo runtime.

To keep that preference but start only the runtime API for one launch, pass the explicit opt-out flag:

npm start -- --noautostart

In Service Admin releases that include the Settings → Startup page, turn off Automatically start enabled services to leave services stopped when the runtime starts; turn it back on to restore the default. The one-launch flag does not change this saved preference.

4. Stop the demo​

From another terminal in the same folder:

npm run demo:stop

You can also press Ctrl+C in the original start terminal. Start again with npm run demo; stopping keeps the workspace data.

Something didn't start?​

Run npm run demo:status for a read-only report. The runtime health endpoint helps distinguish runtime startup from an Admin UI problem. Use the demo operations guide for endpoint URLs, port conflicts, logs, recovery, and reset commands.

Next steps​