Skip to content

MARKDOWN SOURCE

Raw
# Vertical Slices: Once CLI port

1. **CLI tracer:** add `ino once` help and a no-Docker `ino once version` response, wired through the existing `ino` executable.
2. **Discover existing installs:** connect to Docker Engine and make `ino once list` discover/read v0.3.4 Once namespaces, containers, proxy settings, and app labels.
3. **Operate existing apps:** add native `start`, `stop`, and `exec` for discovered apps without replacing containers or volumes.
4. **Deploy a basic app:** pull an image, prepare the Once namespace/proxy/volume, create and health-check an app, and safely retain the previous app on failure.
5. **Complete deploy configuration:** add Once-compatible hostname/TLS, env, SMTP, resource, backup, key, and registry-auth flags and metadata.
6. **Remove and teardown safely:** implement app removal and namespace teardown with explicit, tested volume-retention/deletion behavior.
7. **Create backups:** write v0.3.4-compatible gzip-tar backups, including metadata, `/storage`, hook behavior, pause/unpause safety, and retention.
8. **Restore backups:** validate/extract compatible archives, check host conflicts, run post-restore hooks, deploy, and preserve data on errors.
9. **Update apps and settings:** implement image updates and settings redeploys with rollback, volume reuse, proxy routing, and persisted operation results.
10. **Manage keys:** add Once-compatible key display/set/reset operations and verify generated/serialized key formats.
11. **Self-update Ino:** implement `ino once self-update` through Cargo installation from the project source, isolated so a dedicated script can replace it.
12. **Background operations:** add scheduled update/backup runs and service install/uninstall with detection and explicit handoff from an existing Once service.
13. **Parity and release polish:** verify the full v0.3.4 non-UI CLI surface, strengthen Docker-backed compatibility tests, document supported behavior, and add third-party MIT notices.

Vertical Slices: Once CLI port

  1. CLI tracer: add ino once help and a no-Docker ino once version response, wired through the existing ino executable.
  2. Discover existing installs: connect to Docker Engine and make ino once list discover/read v0.3.4 Once namespaces, containers, proxy settings, and app labels.
  3. Operate existing apps: add native start, stop, and exec for discovered apps without replacing containers or volumes.
  4. Deploy a basic app: pull an image, prepare the Once namespace/proxy/volume, create and health-check an app, and safely retain the previous app on failure.
  5. Complete deploy configuration: add Once-compatible hostname/TLS, env, SMTP, resource, backup, key, and registry-auth flags and metadata.
  6. Remove and teardown safely: implement app removal and namespace teardown with explicit, tested volume-retention/deletion behavior.
  7. Create backups: write v0.3.4-compatible gzip-tar backups, including metadata, /storage, hook behavior, pause/unpause safety, and retention.
  8. Restore backups: validate/extract compatible archives, check host conflicts, run post-restore hooks, deploy, and preserve data on errors.
  9. Update apps and settings: implement image updates and settings redeploys with rollback, volume reuse, proxy routing, and persisted operation results.
  10. Manage keys: add Once-compatible key display/set/reset operations and verify generated/serialized key formats.
  11. Self-update Ino: implement ino once self-update through Cargo installation from the project source, isolated so a dedicated script can replace it.
  12. Background operations: add scheduled update/backup runs and service install/uninstall with detection and explicit handoff from an existing Once service.
  13. Parity and release polish: verify the full v0.3.4 non-UI CLI surface, strengthen Docker-backed compatibility tests, document supported behavior, and add third-party MIT notices.