chore: release 1.2.2
Merge pull request 'feat: deploy Git repos through release jobs' (#9) from t3/remote-repo-deployment into main ## Summary - Run repository checks and releases as background jobs, with live progress and command output in the Deploy tab. - Use the CLI release flow to create or update apps, including version bumps, Git pushes, image builds, and deployment. - Add `--env-file` and `--yes` options to `ino once remote create` for scripted runs. - Update deployment documentation. ## Testing - `cargo fmt --all -- --check` - `cargo clippy --all-targets --all-features` - `cargo test --all-targets --all-features` (110 tests passed) - `cargo doc --all-features --no-deps` - `node --check` on the Deploy UI script - Not run: real registry pushes or deployment against a live Ino server.
feat: deploy Git repos through release jobs - Run versioned releases from the Deploy tab with live progress - Support scripted remote app creation with environment files
Merge pull request 'feat: deploy apps from Git repositories' (#8) from t3/remote-repo-deployment into main ## Summary - Add a Deploy tab flow to clone a Git repository, inspect its image and version, and create or update the matching server app. - Build and push versioned images from the console machine, with configurable hostname, environment, HTTPS, and auto-update settings for new apps. - Document repository deployment requirements and behavior. ## Testing - `cargo fmt --all -- --check` — passed. - `cargo clippy --all-targets --all-features` — passed with no warnings. - `cargo test --all-targets --all-features` — passed (108 tests). - Headless browser checks covered inspect, deploy, create form validation, build-error display, and mobile layout using a fake server and stub Docker; no real image push or VPS deployment was performed.
feat: deploy apps from Git repositories - Add console workflow to clone, build, push, create, and update apps - Document repository deployment requirements
Merge pull request 'feat: log server deployment outcomes' (#7) from t3/log-deployment-outcomes into main ## Summary - Log success and failure outcomes for API deploy, update, and environment changes, including elapsed time and failure reasons. - Document where to find the server logs and what deployment entries contain. ## Testing - `cargo fmt` - `cargo test --bin ino once::server` (8 passed) - `cargo test` (95 passed across test groups) - `cargo clippy --all-targets` (no findings reported for `api.rs`)
feat: log deployment outcomes in server output
chore: release 1.2.1
Merge pull request 'feat: add deploy and all-app log views' (#6) from t3/ui-deploy-logs-tabs into main ## Summary - Add Deploy and Logs views to the console; Deploy is marked as coming soon. - Add searchable, filterable all-app logs with per-app selection, follow, refresh, copy, and timestamp-based ordering. - Add optional RFC 3339 timestamps to the server logs API, with fallback for servers that do not support timestamps. ## Testing - `cargo test` passed (83 unit tests, 10 CLI tests, and 2 server tests). - `cargo fmt --check`, `cargo build --offline`, and `node --check src/commands/once/ui/app.js` passed. - Browser checks verified timestamp ordering and legacy-server fallback. 32 of 33 checks passed; the remaining console-error check flagged expected 404s from the mock server.
feat: add deploy and all-app log views - Add searchable, filterable logs across apps with follow and copy controls - Support timestamped log output in the server API
chore: release 1.2.0
feat: show progress while the CLI waits on long steps Add a spinner module that animates on a terminal and prints one line otherwise, and use it for uploads, image pulls, remote create and update, health checks, and start, stop, remove, backup, restore and teardown. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
chore: release 1.1.0
feat: run the Ino console as a background service `ino once server ui` now has start, stop and run subcommands. `start` runs the console as a detached process, records its PID and port in the Ino state directory, and waits until it answers before returning. `stop` ends it. `run` keeps the old foreground behaviour. `ino ui` is a shortcut for `ino once server ui start`. The per-run token is removed from the console URL and API calls. Browser requests whose Origin is not the console's own origin are refused instead. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
chore: release 1.0.2
fix: include Cargo.lock in the release commit Releases bumped Cargo.lock but left it uncommitted, so a successful `ino` run still had changes to commit. The lockfile is now staged with the rest of the release and the tree is clean afterwards. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
Merge pull request 'fix: resolve Clippy and Cargo warnings' (#5) from t3/fix-clippy-cargo-warnings into main ## Summary - Fix Clippy and Cargo warnings across the Once commands, release flow, and CLI. - Extract helpers and reorganize Docker integration tests to keep code maintainable. - Update the lockfile’s `ino` version to match the package version. ## Testing - `cargo clippy --all-targets --all-features -- -D warnings` — passed. - `cargo build --all-targets --all-features` and `cargo build --release --locked` — passed. - `cargo fmt --all -- --check` and `cargo doc --all-features --no-deps` — passed. - `cargo test --all-targets --all-features` — passed (85 unit tests; other test targets passed). - `cargo test --test once_docker --features docker-tests` — passed (2 tests).
fix: resolve Clippy and Cargo warnings
feat: read the console server URL from INO_SERVER_URL `ino once server ui` takes --server as optional. When the flag is absent or blank, the server comes from INO_SERVER_URL, so the URL can be exported once in the shell profile. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
chore: release 1.0.1
Merge pull request 'chore: update locked Ino version to 1.0.0' (#4) from t3/app-secrets-dashboard into main ## Summary - Update the `ino` package version in `Cargo.lock` to match `Cargo.toml`. ## Testing - `cargo build --release` — passed. - `mise run install` — passed.
chore: update locked Ino version to 1.0.0
feat: manage app environment variables and add a local server console Add GET and PUT /api/v1/apps/{host}/env to read and replace each app's own environment variables. Saving redeploys the app from its current image, keeps Once-managed and server-reserved names, and refuses changes to stopped apps. Add GET /api/v1/apps/{host} for redacted settings and an isServer flag on app summaries. Add `ino once server ui --server <url>`, a loopback console that serves a single-page UI and forwards /up and /api/v1 with the bearer key added locally. Requests need a per-run token and a loopback Host header. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
chore: release 1.0.0
fix: check a server update before routing it and keep the old server answering - Verify a new server container at its own Docker address before switching the proxy. The public URL still routed to the server doing the update, so the check could never pass during a self-update. - Route server apps with proxy::deploy like other apps. - Leave the previous server container to the new server, which removes superseded containers after a grace period. Removing it from the update handler dropped the response to the request that started it. - Check the app's presence before the version bump and image push, so a failed check leaves nothing half-released. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
chore: release 0.5.27
chore: release 0.5.26
chore: update locked Ino version to 0.5.25
chore: release 0.5.25
chore: release 0.5.24
fix: skip binary upload without TWIG_TOKEN and inline the install task - Skip the binary build and upload with a notice when no Twig token is set, instead of failing the release. `ino binaries` skips the same way. - Overwrite stale regular-file `ino` copies on PATH during install instead of failing the task. - Move the install task from mise-tasks/install into mise.toml. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
chore: release 0.5.23
chore: release 0.5.22
Merge pull request 'feat: rewrite ino in Rust and publish binaries' (#3) from t3/a95f6596 into main ## Summary - Rewrite Ino in Rust and preserve the existing CLI and deployment workflows. - Add `ino binaries` to build configured targets and upload them to the Twig registry; integrate uploads with releases. - Port release, installation, and empty-application-list fixes, and update documentation and build tasks. ## Testing - `cargo test --all-targets` — passed (77 + 10 + 2 tests). - `cargo fmt --all -- --check` — passed. - `cargo doc --all-features --no-deps` — passed. - Binary upload against a local mock registry — passed; verified the PUT path, bearer token, and uploaded body. - Real Twig upload, full release, and Docker image build — not run.
feat: rewrite ino in Rust
chore: release 0.5.21
Merge pull request 'fix: check the remote app right before deploying' (#2) from t3/check-remote-app-before-deploy into main ## Summary - Move the remote app-presence check to the deploy boundary in `runRelease`, immediately before `updateDeployment`/`createApp`. - Keep `INO_API_KEY` validation ahead of version bump, image build, and Git side effects by capturing the key up front. - Remove the duplicate pre-check from `ino once remote create` and drop the now-unused `containsHost` helper. - Document in `docs/once-server.md` and `skills/ino-once/SKILL.md` that the server check happens after the image and Git release are published. - Trade-off: a mismatched app state (missing for a release, existing for a create) is only reported after build/push/commit has completed. ## Testing - `zig fmt --check src-zig` - `zig build test`
fix: check the remote app right before deploying Move the app-presence check out of the start of the release and next to the deploy request, so the release no longer blocks on a check taken before the image build. The API key is still validated before any side effects, and `ino once remote create` no longer duplicates the check before its prompts.
fix: uninstall the cargo-managed ino instead of overwriting it Ino is installed to ~/.local/bin now. Leaving a cargo-installed copy in ~/.cargo/bin, which usually precedes ~/.local/bin on PATH, kept old behavior alive. The install task now uninstalls the cargo package (including its metadata) and rejects an INO_PREFIX inside the cargo bin directory.
chore: refresh other ino copies in the install task The task only updated the copy installed to the selected prefix, leaving a stale ~/.local/bin/ino able to answer with old behavior elsewhere on PATH. Refresh both conventional user-level copies and accept a byte-identical resolved binary.
fix: report an empty application list explicitly `ino once list` printed nothing when the namespace had no apps, which looked like a broken command. Print the namespace in a short message instead.
fix: write command output to stdout The Zig port printed help, versions, and operation results with std.debug.print, which writes to stderr. Piping or capturing output (for example the documented `ino once version | awk` snippet) therefore returned nothing. Route normal output through a stdout helper and keep errors on stderr, and add an end-to-end CLI test for the streams.
chore: release 0.5.20
Merge pull request 'feat: overwrite cargo-installed ino and verify the install' (#1) from t3/mise-install-task-overwrite-check into main ## Summary - Replace the inline `[tasks.install]` entry with a mise file task at `mise-tasks/install`, so the task can do more than a single `zig build` command. - Install over an existing cargo-installed `ino` in `$CARGO_HOME/bin`, since that directory usually precedes `~/.local/bin` on PATH and would otherwise keep shadowing the fresh build. - Fall back to `$INO_PREFIX/bin` when set, then to `~/.local/bin`. - After installing, check that `ino` on PATH resolves to the newly installed file and reports the version from `build.zig.zon`, failing with an actionable message on a stale or shadowing binary. - Document the overwrite behavior, the verification step, and the `INO_PREFIX` override in the README. ## Testing - `mise run install` — installed the current build over the stale cargo binary and printed the verified `ino <version>` output. - `mise run install` with `INO_PREFIX` pointing at a directory not on PATH — exits 1 and reports the binary that actually shadows the install. - `mise run verify` — formatting check, Zig test suite, and release build all pass.
feat: overwrite cargo-installed ino and verify the install - Replace the inline mise install task with mise-tasks/install - Install over an existing cargo-installed ino so PATH stops returning a stale build - Fail when ino resolves to another binary or reports a version other than build.zig.zon - Document INO_PREFIX and overwrite behavior in the README
chore: add a mise install task
chore: remove the legacy Rust implementation
fix: hide the remote API key prompt
docs: describe the Zig implementation and Docker CLI runtime
test: cover Zig manifest, label, tar, and environment parsing
docs: install Ino from source with Zig
chore: release 0.5.19
fix: keep the server command buffer alive during container creation
chore: release 0.5.18
fix: start the server listener before proxy deployment
chore: release 0.5.17
feat: rewrite ino in Zig
chore: release 0.5.16
chore: trim unused actix-web features from Cargo.lock
feat: replace remote ensure with interactive remote create - Rename `ino once remote ensure` to `ino once remote create` - Prompt for the server API key (hidden) and app environment variables - Release the project and create the app from the pushed image in one run - Check app presence before release so update and create fail early - Show server error codes when app list, create, or update requests fail - Document the new first-deploy flow in README, server guide, and ino-once skill
feat: pass .ino.env settings to remote app on ensure - Read every KEY=VALUE line in .ino.env (except INO_API_KEY) as the app environment - Prefer INO_API_KEY from the environment over .ino.env - Send the env map in the POST /api/v1/apps settings - Update the env template and docs to describe the new behavior
chore: release 0.5.15 - bump crate version in Cargo.toml - update ino entry in Cargo.lock
chore: release 0.5.14
chore: release 0.5.13
chore: release 0.5.12
chore: release 0.5.11
chore: release 0.5.10
chore: release 0.5.9
chore: release 0.5.8
chore: release 0.5.7
chore: release 0.5.6
chore: release 0.5.5
chore: release 0.5.4
chore: release 0.5.3
docs: plan ino VPS server
chore: release 0.5.0
feat: port Once CLI into ino once
chore: release 0.4.5
clean up
chore: release 0.4.4
chore: release 0.4.3
chore: release 0.4.2
chore: release 0.4.1
chore: release 0.4.0
feat: semver
README: readme.md
Initial commit