Assets were skipped only when name and size matched. A rerun rebuilds the
binaries, whose sizes differ by a few bytes, so v1.13.0's rerun attached ten
duplicates the published checksums do not describe. Skip by name.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
compose up -d leaves NATS on its old config when only the bind-mounted
nats.conf changed, so the 8 MB max_payload never applied on upgrades.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- PUBLIC_SERVER_URL and TRUSTED_HOSTS left at .env.example's sample
(control.example.com, any RFC 2606 name) are ignored with a startup
warning: links follow the forwarded headers and devices download from
the server URL they already use. .env.example ships them empty and
deploy.sh clears sample values from an existing .env.
- The screen host is built from its own folder so .cargo/config.toml's
+crt-static applies; the shipped exe imported VCRUNTIME140.dll and died
without output on devices without the Visual C++ runtime ("the screen
host gave no answer"). The build now refuses an exe with CRT imports.
- A failed screen host probe is retried with backoff (30 s up to 10 min)
and the inventory is republished once it answers; the warning and the
reason carry the exit code.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Release of the work since v1.6.1: bundled Postgres by default, Restart After Run with an agent-held timer and optional warning, S3 pre-run downloads, parallel dispatch and batched job states, script sequences, parallel upgrade fan-out and the reconnect storm fixes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
docker-compose.yml gains a postgres service (EXECUTER-DB-00001, official
image pinned by major and digest like NATS, INTERNAL network only, no host
port, pg_isready health check, shm_size, runs as PUID:PGID, data in
${STACK_BINDMOUNTROOT}/${STACK_NAME}/Postgres/Data). It is in the "postgres"
Compose profile; COMPOSE_PROFILES in .env turns it on, and the backend waits
for it healthy (depends_on required: false, so SQLite and external databases
start without it). The backend defaults to DATABASE_PROVIDER=postgres with
DATABASE_CONNECTION_STRING and DATABASE_PASSWORD from .env.
docker-compose.postgres-port.yml publishes a host port, opt-in through
POSTGRES_BIND.
deploy.sh decides the database: what .env names when the operator set it;
else SQLite when API/Data/app.db exists (written to .env, with a note on how
to move); else the bundled Postgres, its password generated into .env (and
exported), never regenerated over an existing database. COMPOSE_PROFILES
follows. The decisions are functions that scripts/tests/Test-DeployDatabase.sh
runs on fixtures without Docker. Compose 2.20.2+ is checked; a new .env is
mode 600. New-LocalSecrets.ps1 generates the password for a new .env and
keeps an existing .env's database settings on -Force.
README: deploy, secrets, Compose, database providers, Postgres backups and
pg_restore, and Moving from SQLite to Postgres (migrate-database).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The server MSI's wizard is now Welcome > Folders > Database > Certificate >
Server Address > Ready, after StifleR's flow:
- Folders: install, data, log and backup folders with Browse (defaults follow
a changed install folder), Enable Windows Long Paths while they are off.
- Database: SQLite, PostgreSQL (host, port, database, SSL mode, user,
password) or SQL Server (server\instance, port, database, Windows or SQL
login, Encrypt, Trust Server Certificate), Create If Missing, and Test
Connection with the server's own error; Next needs a passing test or
Continue Without a Successful Test.
- Server Address: HTTPS port and an HTTP redirect port, Listen On all or one
of this computer's addresses, NATS and object store ports, public URL,
firewall rules; a port in use names the program holding it.
Every choice is a public property (DATAFOLDER LOGFOLDER BACKUPFOLDER
ENABLELONGPATHS DBPROVIDER DBSERVER DBPORT DBNAME DBAUTH DBUSER DBPASSWORD
DBSSLMODE DBENCRYPT DBTRUSTCERT DBCREATE DBSKIPTEST HTTPREDIRECTPORT
OBJECTSTOREPORT PUBLICSERVERURL FIREWALL), checked the same way for /qn
before anything changes. The custom actions test PostgreSQL with their own
protocol client (SCRAM-SHA-256, MD5, SSL) and SQL Server with
System.Data.SqlClient, create the database when the account may (and give
the service's Windows login db_owner), write appsettings.json in place, keep
the password DPAPI-protected and out of the log, restrict the file and new
folders to SYSTEM and Administrators, create long folders through \\?\, and
keep netsh firewall rules for the ports in effect.
Upgrades find the install folder again, keep the configuration and change
the database only when the command line gives another; the choices but the
password are remembered for a reinstall. The banner and Welcome/Finish
artwork are drawn from the product icon by Generate-Icons.ps1.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Being Viewed banner was WinForms published as a self-contained single
file (49.3 MB, ~320 ms just to start and exit). It is now plain Win32 through
source-generated LibraryImport (runtime marshalling disabled, no reflection)
published with Native AOT: 1.6 MB for win-x64 and win-arm64, ~33 ms to start
and exit (the OS process floor), on screen in ~0.1 s.
- BannerWindow: a WS_EX_TOPMOST | TOOLWINDOW | NOACTIVATE popup, a STATIC per
caption (read by screen readers, clicks fall through to drag) and an
owner-drawn BUTTON per Stop, named for its session; the mouse is handled in
a subclass and BM_CLICK invokes directly, so clicking or assistive-tech
invoke never activates the banner. GDI drawing, comctl32 6 tooltips,
PerMonitorV2 manifest with WM_DPICHANGED, AppsUseLightTheme and high
contrast on WM_SETTINGCHANGE, DWM rounded corners and dark frame.
- Same metrics, colours and wording as the WinForms banner (checked against
screenshots at 125%), now in window-free Logic/ (layout, palette, rows)
that Agent.Tests compiles and tests.
- The protocol moves to src/Shared.Banner (compiled into agent and banner),
with the exit codes; DLL hardening, pipe checks and protocol unchanged.
- Package-Agent publishes the banner with AOT when vswhere finds the MSVC
tools for the RID (and puts vswhere on PATH for newer VS vcvarsall),
otherwise warns and publishes a trimmed single file (~11 MB).
- README: Build Tools "Desktop development with C++" (plus ARM64 tools) as a
prerequisite, also for the CI windows-host runner.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A VPS running only ExecuteR puts its edge on the standard ports; the app
services stay on their upstream ports on loopback. The HTTP redirect and the
deploy summary name the HTTPS port only when it isn't 443.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- ADMX/ADML "Remote View: show the Being Viewed banner" (RemoteViewBanner,
REG_DWORD, default off); MSI property REMOTEVIEWBANNER.
- Package-Agent publishes ExecuteR-Banner.exe (self-contained single file)
into every Windows zip; the MSI installs it under Program Files when
present (HasBanner). The Windows PE portable install removes it.
- Generate-Icons also renders banner.ico from assets/banner-icon-source.png.
- Console: Remote View page shows "Banner On" when the device will show the
banner.
- README: Being Viewed banner (policy, behaviour, security model), policy
and MSI tables, packaging; third-party notices list Windows Forms.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scripts/tests/Test-Branding.ps1 reads each exe's first RT_GROUP_ICON and
compares its frames byte for byte with assets/icons/app.ico, and checks the
version resource names description, product, company, copyright and
version. README: where the icon lives, how executables get it, how to
regenerate it; ImageMagick is no longer a prerequisite.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
build.rs embeds assets/icons/app.ico and a version resource through
winresource (MIT, build dependency only, rc.exe from the Windows SDK):
FileDescription "ExecuteR Screen Host", ProductName "ExecuteR", company
and copyright read from Directory.Build.props. The version is the build's
one version (EXECUTER_VERSION, which Build-ScreenHost.ps1 -Version sets and
Package-Agent passes), else Cargo.toml's. The binary had neither before.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scripts/Generate-Icons.ps1 now renders assets/icons/app.ico from
assets/icon-source.png with System.Drawing (no installs, Windows PowerShell
or pwsh, byte-identical across runs): 16, 20, 24, 32, 40, 48, 64 and 128 px
as 32-bit DIBs and 256 px PNG-compressed (124 KB, was 370 KB with six
uncompressed frames).
The .ico is committed and every build embeds it, so local builds match CI.
The packaging scripts and workflows no longer generate it at build time
(the ImageMagick step wrote artifacts/icons/app.ico, which nothing read):
-SkipIcon and the release "Generate icon" step are gone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Build src/ScreenHost (Rust, x86_64-pc-windows-msvc) in Package-Agent and
put ExecuteR-Screen.exe in the win-x64 zip (also the Windows PE package
and agent upgrades) and the MSI; CI and release install Rust first. Both
skip cleanly while src/ScreenHost is not in the tree. Remote View policies
in the ADMX (and MSI properties for the on/off ones); the AllowFileAccess
policy key gets its missing backslashes back.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
deploy.sh sourced .env before the keys existed, so the shell's empty values
overrode the keys it then wrote; and compose reads .env beside the first
compose file, so a manual upgrade ran without them too. Keys are now written
and exported on every run, compose gets --env-file, and IaC/compose/.env links
to the stack's .env. The deploy waits on /api/ready and says what is missing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
App ports (backend, webui, NATS WS) now publish on 0.0.0.0 by default so an
edge proxy on another host can reach them without extra config. deploy.sh
--with-proxy flips an unset BIND_EXTERNAL_ADDRESS to 127.0.0.1, since the
bundled proxy reaches services over the compose network. An explicit value
always wins.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
NATS resolves `include` paths relative to the config file's own directory,
so `include /etc/nats/resolver.conf` became /etc/nats/etc/nats/resolver.conf
and the server exited on startup ("no such file or directory"). Use the
relative `include resolver.conf`, which resolves to /etc/nats/resolver.conf
where it is mounted.
The backend and webui run as PUID:PGID (default 1000) but the bind-mount
data tree was created root-owned, so the backend could not write /data.
chown the stack's data tree to PUID:PGID after creating it. NATS runs as
root and is unaffected.
Neither file is baked into an image (nats.conf is mounted, deploy.sh is
fetched), so no rebuild is needed — [skip ci].
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The backend image runs as a non-root user, so the key-gen container could
not write operator.nk et al into the root-owned secrets/nats bind mount
(UnauthorizedAccessException / Permission denied), failing a fresh deploy.
Pass --user "$(id -u):$(id -g)" so the ephemeral container writes as whoever
runs deploy.sh — the same identity that created the directory — so the keys
always land. The runtime services keep their own non-root users.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
An empty INITIAL_ADMIN_PASSWORD now means generate and record: the one-time
password goes to <data>/initial-admin-password.txt (Administrators, SYSTEM and
the server's own account only; mode 600 elsewhere) and the log only says where.
The file is removed once the password is changed or reset. reset-admin (alias
auth-reset) reads the standalone appsettings.json, so it reaches the same
database with the service running or stopped, takes --user/--password, turns
the account back on and is audited. The compose scripts stop generating the
password into .env.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Silo is pinned by SHA-256 in build/object-store.json and goes into the standalone
packages, the MSI and the backend image, with its licence. Releases carry its
source. The Swarm and Kubernetes stacks run one store as an internal service.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
scripts/tests/Test-Versioning.ps1 (plain asserts, no Pester): the version
rules against canned git describe output and the limits, then a scratch
SHA-256 repository with a bare origin walked through the seed: calendar
tags ignored, no release tag refused, v0.1.0 plus a breaking change
releases 1.0.0, a re-run of the tagged commit is 1.0.0 again, builds after
it are 1.0.0.N, docs alone release nothing, a fix 1.0.1, a feat 1.1.0, a
branch other than main is refused.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Build, Test and the packaging scripts take the version from
Get-Version.ps1 and the short commit from the same place. Both MSIs get
the four-field version as ProductVersion (X.Y.Z.0 for a release, X.Y.Z.N
between releases) instead of the calendar transform. Checksums and release
assets take only their own version's files (1.4.0 no longer matches
1.4.0.7's).
Publish-Release.ps1 creates the tag vX.Y.Z on the released commit and the
release "ExecuteR X.Y.Z" with semantic-release's notes (-NotesFile,
-Prerelease), reuses both on a re-run of the same commit, refuses a version
already tagged on another commit and skips assets uploaded whole.
deploy.sh builds from source with the git version (0.0.0.0 without git)
and runs the images it built by that tag. Test.ps1 runs the watchdog
tests too.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Releases are X.Y.Z from git tags vX.Y.Z; builds between releases are
X.Y.Z.N, N commits after the last release (git describe, 1-3 digit majors
only, so the calendar-era tags never count); with no release tag reachable
a build is 0.0.0.<commits>. Every version is 3-4 numeric fields, refused
when it does not fit an MSI ProductVersion or has a calendar-era major.
scripts/Get-Version.ps1 computes it (Get-UnifiedVersion.ps1 stays as the
old entry point). scripts/Get-NextRelease.ps1 runs semantic-release in
dry-run mode (pinned in build/release, conventionalcommits preset, main
only) for the version a release publishes, or for nothing when the commits
since the last release call for none. Directory.Build.props stamps
four-field assembly/file versions and InformationalVersion
X.Y.Z[.N]+<short commit>; a build not handed a version reads it from git
(build/Version.targets), otherwise 0.0.0.0.
BREAKING CHANGE: versions are no longer yyyy.MM.dd.HHmm. The first release
after the seed tag v0.1.0 is 1.0.0, which every comparison orders after
every calendar-era version.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Package-Agent.ps1 publishes the watchdog (trimmed single file) for every RID
and puts it beside the agent (ExecuteR-Watchdog.exe; executer-watchdog on
linux/macOS), so the zips CI stages into the backend image carry it. The MSI
installs it as its own component with the ExecuteRWatchdog service
(LocalSystem, automatic, restart on failure, `run`), started on install and
removed on uninstall; MajorUpgrade is unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The MVP design spec (read by coding agents as guidance) now describes
the React/MUI console on the Mantis Pro shell: stack, folder layout,
live-update path, UI conventions, image build (Vite dist/ served by
server.mjs), CI step and architecture diagram, so later work does not
drift back to Svelte.
- .editorconfig covers .tsx/.mjs instead of .svelte; Test.ps1 help names
the WebUI typecheck + lint.
- Initialize-Repository.ps1 refuses Node older than 22 up front (the NATS
browser client needs it; npm's engines check already enforced it later).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The project is not open source, so the AGPL text no longer describes it.
- LICENSE: the Grace Solutions proprietary licence used by the other house
products, including the clause for the commercially licensed Mantis Pro
template the console is built on.
- THIRD-PARTY-NOTICES.md: the commercial template, the bundled nats-server
and the open-source server, agent, console and build components with
their licences.
- Assemblies carry the copyright; the WebUI package is UNLICENSED; both
container images are labelled LicenseRef-GraceSolutions-Proprietary.
- Server and agent zips ship LICENSE and THIRD-PARTY-NOTICES.md; the README
gains a Licence section.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Replaces the SvelteKit app with a Vite/React 19 console built on the Mantis
Pro 4.2.0 seed (MUI 9.0.1): its theme system, component overrides, drawer
and header, restyled to the slate surfaces and blue accent of the house
consoles, with light/dark/system modes on CSS variables.
This commit is the shell; pages move over in the commits that follow
(routes show a placeholder until then).
- Session context with can(permission); navigation entries the session
cannot use stay visible, disabled, and say why on hover.
- One API module (cookie auth + CSRF double-submit; a 401 returns to
sign-in with a safe returnUrl) and SWR for cached, shared reads.
- The browser NATS client is unchanged apart from exposing its connection
state to React; the header shows it as Live/Connecting/Offline.
- Shared building blocks: PageHeader, DataTable (sort, paging, row
selection, toolbar slot), TreeList (keyboard, context menu, drag and
drop), ActionMenu (menus as data, greyed entries explain themselves),
ConfirmDialog, Sheet, GatedButton, StatusChip and time/format helpers.
- Sign-in keeps local, OIDC, auto-redirect, ?local=1 and the forced
first-password change.
Build/deploy: `vite build` writes dist/. The webui image now serves it
with a dependency-free server.mjs (SPA fallback, immutable asset caching,
traversal-safe) on the same port 3000, so compose/k8s/swarm and their
health checks are unchanged; Package-Server embeds dist/ instead of the
adapter-static output. `npm run check` is now typecheck + ESLint.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The images job recomputed the version with its own `date` clock while build-test
used Get-UnifiedVersion, so a build spanning a minute landed the container images
and the binaries a minute apart (e.g. ...1041 vs ...1042).
- Get-UnifiedVersion now derives the version from the HEAD commit's committer
time (UTC) when not given one explicitly, so every job and workflow building
the same commit computes the same version — deterministic, reproducible.
- The images job no longer recomputes: build-test exposes its version as a job
output and images consumes needs.build-test.outputs.version.
- release.yml already calls Get-UnifiedVersion, so it now matches ci.yml for the
same commit too.
Verified locally: the version equals the HEAD commit time, is stable across
calls, and an explicit -Version / UNIFIED_VERSION still wins.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The published binary was Agent.exe, so its rolling log was Agent-<date>.log.
Set the assembly name to ExecuteR-Agent, so the binary is ExecuteR-Agent.exe
and the log (named after the running executable) becomes
ExecuteR-Agent-<date>.log. Updated the MSI harvest + service/purge custom
actions, the enrollment install script, the packaging unix-rename source, the
Branding constant, the CLI usage string and the README. Unix still ships as
executer-agent. Agent builds (both TFMs) and its 60 tests pass.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Agent trust for self-signed servers is now abstracted from operators.
The server exposes its public CA chain at GET /api/enrollment/ca; a new
pinned trust mode (TlsTrustMode=pinned) makes the agent fetch, pin,
install and validate against that CA for both enrollment HTTPS and the
NATS WebSocket, and a background CaRefreshService re-pins it across
renewals so trust never lapses. Install scripts, the agent MSI
(TRUSTMODE property), the ADMX template and the Add Device modal all
drive pinned trust for self-signed servers; skip-verify/insecure
remains an escape hatch.
Backend ingest subscriptions (presence, inventory, agent events, job
output/progress) now use a NATS queue group, so multiple backend
replicas share the load instead of each writing duplicates.
Deployment manifests move to IaC/: compose (moved from root, paths
rebased; deploy.sh and docs updated), swarm (replicated stack: Postgres,
3-node JetStream cluster, API replicas + single scheduler worker, shared
key-ring volume), and k8s (namespace/config, Postgres + NATS
StatefulSets, API Deployment + HPA, single worker, WebUI, ingress).
Wiki gains a Scaling and HA page with an HA topology diagram covering
stateless vs stateful tiers, NATS cluster/supercluster, overlay
(Tailscale/NetBird), shared storage (MicroCeph) and service discovery.
Verified: solution builds, Backend 100 / Agent 60 tests, svelte-check
clean, agent + server MSIs build.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Standalone setup fixes the jetstream double-nesting (store_dir is the
parent), moves the database to data/db and logs to ./logs; the agent
logs to ./Logs next to its binary. Both MSIs install under
ExecuteR\Server and ExecuteR\Agent, binaries carry ExecuteR
Server/Agent product metadata with dateversion-shortcommit as the
product version, and shipped bundles drop pdbs and the staticwebassets
manifest.
Execution reworks: targets are an add-one-or-more chip list (devices
and groups mix; each run lands in one per-device list with focusable
output), the script page gains a History section, the device page's
tab becomes Execution History grouped by script, and JOB_HISTORY_LIMIT
(default 200 per device, 0 off) prunes old jobs plus their stored
output. Functions drops the Module name placeholder and only opens the
editor on selection or New function.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
MSIs, ZIPs and checksum files rename to ExecuteR-Agent-* and
ExecuteR-Server-* across the packaging scripts, the CI staging/upload
globs and the release asset filter. The agent-package bundle names the
server serves (Agent.msi, Agent-<rid>.zip) are internal delivery paths
and stay unchanged. Takes effect on the next release build.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Service processes capture PATH at start, so Get-Command missed both
magick and winget on the CI runner even though they are installed.
The script now probes the usual install locations directly (Program
Files, WinGet links, per-user WindowsApps for winget itself), and the
winget exit code is no longer fatal - "already installed / no upgrade"
returns non-zero; what matters is whether magick.exe exists after.
Verified locally with a stripped PATH simulating the service session.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The install endpoint takes skipVerify=1 instead of auto-detecting: a
self-signed server that later gains a proxy with a real certificate
must not leave agents skipping validation needlessly. The Add Device
modal and the Settings token panel gain a checkbox, pre-selected only
while the server serves its self-signed chain directly. The PowerShell
skip snippet now covers both generations: wildcard
-SkipCertificateCheck defaults on 7+, the ServicePointManager callback
on 5.1 (verified live in both shells).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
TLS_SELF_SIGNED defaults on everywhere (0 / setup --tls 0 / unchecking
the pre-checked MSI box opts out); the compose stack alone keeps its
internal hop plain HTTP by default because the bundled nginx site
proxies http upstreams. On Windows the machine stores stay
authoritative, but every chain settle now also mirrors certs, keys and
fullchain.crt to <data>/tls (keys marked exportable for refresh) so a
local Caddy / Nginx UI / nginx can bind or trust the files and
renewals keep them current. Test hosts opt out to avoid chain
generation racing across parallel fixtures.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
TLS_SELF_SIGNED=1 (env/appsettings), setup --tls 1, or the new MSI
checkbox switch the listener to HTTPS with a managed ECDSA chain —
root > intermediate > leaf, issued on first boot, auto-renewed ahead
of expiry and hot-swapped via Kestrel's certificate selector without
a restart. Windows persists the chain in the machine stores (Trusted
Roots / Intermediate CAs / Personal, so local browsers trust it);
Linux/macOS/containers use PEM files under <data>/tls with a
fullchain.crt for pinning. Reverse proxies either skip verification
(the hop stays encrypted — the roots just aren't distributed) or
import root+intermediate, re-importing when the chain rotates.
The MSI finish link follows the checkbox to https; short port flag
aliases keep the setup command inside the 255-char CA column, and the
quoted empty ENABLETLS keeps unchecked installs on plain HTTP.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
`setup` gains --http-port (default 9080), --bind (default 0.0.0.0, IPv6
literals bracketed automatically), and --nats-port/--nats-ws-port/
--nats-monitor-port for the loopback-only sidecar listeners — all
flowing into the generated nats.conf and appsettings.json, with the
sidecar health poll reading NATS_MONITOR_URL instead of a hardcoded
8222. `service install|uninstall --name <n>` registers instances side
by side (Windows service or systemd unit). One directory per instance
owns its config, database, keys, NATS state and agent packages, so
instances never share anything. Re-running setup over existing config
now says so instead of silently keeping old ports.
Verified live: setup with custom ports produced matching nats.conf and
appsettings values, and --bind 127.0.0.1 landed in Urls.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The Windows and Linux binaries are the same backend, so they already
honor the private-network trust defaults; setup now pre-writes the
optional keys — PUBLIC_SERVER_URL, TRUST_PROXY, TRUSTED_NETWORKS,
TRUSTED_HOSTS — as empty placeholders in the generated appsettings.json
(empty means unset everywhere), and QUICKSTART/README explain the
configuration model: flat keys in appsettings.json next to the binary
or the same names as environment variables, env winning.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Devices gains an Add device modal (visible with settings.manage): a
horizontal Windows / Linux / macOS selector, a single-use or multi-use
token choice (24-hour expiry), and Generate command — nothing is
created until confirmed; Esc, click-outside or Cancel dismiss without
side effects, and each open starts fresh. The generated one-liner is
copy-ready per platform.
The install endpoint grew unix variants: ?type=linux|osx returns a bash
script that detects the architecture, downloads the matching agent zip
from the same origin, unpacks to /opt/executer/agent, configures
enrollment through the agent''s new cross-platform `configure --url
--token` verb (registry on Windows, agent.json elsewhere) and registers
the systemd unit / launchd daemon. The agent package service serves the
four unix zips alongside Agent.msi/Agent.zip, and both the CI image
bake and the standalone server bundles stage them.
Covered by seven endpoint tests (PowerShell variants, bash variants
with arch detection, token refusal); modal verified live — it issued a
real token and built the Linux one-liner in the shot.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
No flags needed: setup writes the admin/admin sign-in by default (the
flags remain as overrides), prints the first sign-in guidance, and the
server MSI wizard matches with lowercase admin/admin defaults.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
setup now lives fully in the binary to suit every platform: it accepts
--admin-user/--admin-password (written into appsettings.json on first
run only), downloads nats-server for the current OS/architecture when
the sidecar is absent (zip/tar.gz, BCL only), and wires
AGENT_PACKAGE_PATH at the bundled agent-package directory. Bundles ship
Agent.msi + Agent.zip + VERSION next to the server, so the URL install
command works immediately instead of reporting Missing. Direct binaries
are named ExecuteR-Server(.exe); container names are unchanged. The
committed icon (assets/icons/app.ico) embeds in every build, CI
included.
New Windows installer (src/Installer.Server): harvests the whole
bundle, shows an Administrator account page (defaults Admin/Admin,
ADMINUSERNAME/ADMINPASSWORD properties for silent installs), then runs
the binary''s own `setup` and `service install` — idempotent, so
upgrades and repairs never overwrite existing configuration. Uninstall
stops and removes the service. Verified end to end: MSI carries all 169
files, setup from a bare directory downloaded the sidecar, and the
booted server answered ready (db+nats+signing), signed in Admin/Admin,
served the SPA and reported the bundled Agent.msi with version and
SHA-256.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Skips Invoke-WebRequest progress-rendering overhead; the gallery
redirect is followed automatically.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The PowerShell SDK ships only the core engine modules, so gallery
access on a bare endpoint depended on whatever happened to be
installed. Package-Agent now stages pinned PSGallery downloads
(PSResourceGet 1.2.0, Archive 1.2.6, ThreadJob 2.2.0) into a Modules
directory next to the binary for every platform, the MSI installs it,
and the agent prepends it to PSModulePath — covering the embedded
engine and, via process-environment inheritance, Windows PowerShell
5.1 child processes too. Install-PSResource needs no NuGet-provider
bootstrap, and AllUsers installs land on the standard module path
where later jobs resolve them.
Verified in the embedded host with only the bundled directory on the
path: PSResourceGet loads and reports PSGallery, Compress-Archive
produces a zip, Start-ThreadJob round-trips. Also drops the payload
trim rules for modules the SDK no longer ships.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Package-Agent gains -Runtimes and picks the right flavor per RID
(net10.0-windows for win, portable net10.0 elsewhere) — this also fixes
publishing after the multi-targeting change, which requires an explicit
framework. Unix binaries ship as executer-agent; the MSI still harvests
the win-x64 output.
CI packages the agent for win-x64/linux-x64/linux-arm64/osx-x64/
osx-arm64 plus the combined standalone server (win-x64, linux-x64) and
uploads everything as a "binaries" artifact with checksums. Releases
attach the same set (Server zips included), and the release workflow
sets up Node 22 for the static WebUI build the server bundle needs.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
`Package-Server.ps1` produces a self-contained single-file ExecuteRServer
per platform (win-x64/linux-x64) that embeds the WebUI as a static SPA
(ADAPTER=static build; SSR disabled — the app is fully client-driven),
relays /messaging/agent and /messaging/browser over WebSocket to a
bundled nats-server sidecar it supervises (spawned before the NATS
client connects, restarted with backoff, killed on shutdown), and runs
as a Windows service or systemd unit via `service install|uninstall`.
`setup` generates the NATS operator keys, sidecar config (relative
include paths — nats-server mangles Windows drive-letter absolutes) and
appsettings.json. Windows publishes carry the app icon.
Verified end to end from the packaged zip: setup → run → SPA served,
/api/ready shows natsConnected:true, admin login 200, and a WebSocket
to /messaging/browser receives the NATS INFO greeting through the relay.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
CI service accounts have no winget; the icon is cosmetic and the MSI
compiles without it, so skipping beats failing the whole package step.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>