3
Installation
gsadmin edited this page 2026-08-09 12:33:28 +00:00
This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Installation

Three ways in, easiest first.

Every Gitea release carries the full asset set: agent ZIPs for six platform/arch combinations, both MSIs, the server ZIPs, and SHA-256 checksums.

Windows Server MSI

Run ExecuteR-Server-<version>.msi. The wizard has two pages.

Administrator account — defaults to admin / admin. If you keep the default password, the first sign-in forces a reset.

Network settings — the bind address (0.0.0.0), the HTTP port (9080), the three loopback-only NATS ports, and an Enable Self-Signed TLS checkbox, checked by default. See Networking and TLS for what that does.

When the install finishes, a checkbox offers to open the console in your browser. Wildcard binds resolve to localhost; a concrete bind address opens directly.

Silent installs pass the same values as properties:

msiexec /i ExecuteR-Server-<version>.msi /qn ADMINUSERNAME=ops ADMINPASSWORD=... HTTPPORT=9080 ENABLETLS=1

Upgrades never overwrite existing configuration. Uninstall stops and removes the service. The MSI installs exactly one instance — for several instances on one box, use the ZIP.

Standalone ZIP (Windows / Linux)

ExecuteR-Server setup              # keys, sidecar config, appsettings.json
ExecuteR-Server                    # run in the foreground
ExecuteR-Server service install    # Windows service / systemd unit

Useful setup flags:

  • --admin-user / --admin-password — the initial sign-in
  • --bind — listen address, 0.0.0.0 by default
  • --http-port, --nats-port, --nats-ws-port, --nats-monitor-port — the ports
  • --tls 0 — opt out of Self-Signed TLS

For extra instances on the same machine: one directory each, distinct ports, and service install --name <name>.

Agent installers ship inside the bundle under ./agent-package, so the URL install command works immediately.

Docker Compose

cp .env.example .env    # fill INITIAL_ADMIN_PASSWORD + NATS seed (or run scripts/New-LocalSecrets.ps1)
docker compose up -d --build
Service Container Host port Internal
nats EXECUTER-NATS-00001 19222 (WebSocket) 4222 TCP, 8222 monitor
backend EXECUTER-API-00001 19080 8080
webui EXECUTER-WEB-00001 13080 3000

Put your reverse proxy on :443 in front. The routes are listed in Networking and TLS, and a ready-to-adapt nginx site is in src/Infra/nginx.

First sign-in

Sign in locally as admin / admin, or with the values you chose.

A defaulted password walks straight into a set-new-password form before any session is issued. After that, add your first device: Devices → + Add device (Agent Deployment).