Repository navigation
Nimbo 0.3.0
Pre-release
Pre-release
Changed
- A real desktop app, rewritten in Go. Nimbo is now a Wails app: it opens its own window (no browser, no Java), keeps an icon in the tray, runs a single instance and is about 14 MB instead of a 43 MB installer with its own Java. The React UI is the same. The backend was ported from Kotlin to Go keeping the API and its JSON, and the tests were ported with it. The MSI keeps the old upgrade code, so it replaces a 0.2.x install in place.
- The standalone build is a binary (
nimbo serve) instead of a jar; the Docker image runs it. The distribution kinds are nowbinary,desktopanddocker.
Added
- Configuration files for any stack. The Export drawer writes a
docker-compose.yml(+ its.env) to run a stack without Nimbo, and connection files for your own application: Spring Bootapplication-nimbo.yml, .NETappsettings.Nimbo.json, plus the existing.env, OpenTofu override and AWS CLI profile. Verified by bringing a generated compose up with real containers and using the generated credentials. - Stacks of your own, created, edited and deleted in the app, saved in the data folder and included in backups.
- Cross-site protection. Requests that change something are refused when a web page from another site sent them.
- Emulator variables. Every emulator lists what it can be given and says when it needs nothing. New optional settings: a Redis password (
requirepass, read from the environment so it never shows in the command line), a k3s cluster token, an Azurite account and the PostgreSQL user and database. Initialize generates what is missing, Show reveals a value on request (journaled by name only), Apply recreates a running emulator with the new values keeping its data, and the client variables of an emulator (DATABASE_URL,REDIS_URL, the Azurite connection string) follow the settings, with placeholders until you ask to see the passwords. A card that cannot start says what it needs and offers Initialize and start. - A data folder. Settings, lab progress, usage statistics, a journal and the fidelity history are kept in
~/.nimbo(NIMBO_DATA_DIR), with backup, restore and reset. Lab progress and the language/theme move from the browser to that folder (what the browser had is imported once). - Keep emulator data. A per-emulator switch keeps its data in a Docker volume across stop and remove; deleting it is a separate confirmed action. Verified with real containers for Redis, PostgreSQL, MinIO and Floci AWS.
- Passwords in the Windows store (DPAPI, per user) for MinIO and PostgreSQL; the environment still wins. Never part of a backup.
- Updater. Checks GitHub (at most once a day, or never in manual mode), downloads the installer for your installation verified against
SHA256SUMS, installs the Windows app after you confirm, and imports an installer from a file for offline use. - Offline images. Releases publish the emulator images as
docker savepacks;packaging/make-offline-kit.ps1builds a carry-around kit and System > Offline loads the packs. - A System section with Activity, Settings and data, Updates and Offline screens.
Fixed
- MinIO could not start: its images are no longer published on Docker Hub or quay.io; Nimbo now uses the Chainguard build (
cgr.dev/chainguard/minio). - A malformed JSON body now answers 400 instead of 500.