Skip to content

v0.2.52

Choose a tag to compare

@sling86 sling86 released this 15 Jun 15:15
· 4 commits to main since this release

its v0.2.52

Platforms: Windows (x64) · Linux (x64)

Quick install

Linux (drops its into ~/.local/bin):

curl -fsSL https://github.com/sling86/its-releases/releases/latest/download/install.sh | bash

Windows (drops its.exe into %LOCALAPPDATA%\Programs\its and adds it to the user PATH):

irm https://github.com/sling86/its-releases/releases/latest/download/install.ps1 | iex

Or download ItsSetup.exe for the Inno Setup installer.

Full asset list below. docs/ · CHANGELOG.md · LICENSE — all auto-synced into this repo on every release.

Changes

Added

  • its dokploy apps env-runtime <app> [--show-values] [--diff] — read the env
    vars actually present in the running container (via docker exec printenv),
    the ground truth versus the saved record. --diff flags vars saved in the
    record but missing from the container (the un-applied / Swarm-freeze case) and
    runtime-only vars. Values redacted by default.
  • its dokploy apps apply-env <app> — make a saved env change actually reach
    the container. On Docker Swarm a plain redeploy does not converge
    env-only changes; this stops the app (removes the swarm service), redeploys so
    Dokploy recreates it from the current env, then verifies every saved var is
    live. Brief outage.
  • its dokploy env set <app> … --deploy and its dokploy env unset <app> <KEY…> [--deploy]--deploy saves then recreates the swarm service and
    verifies the change landed. A plain set/unset now warns that the change is
    record-only until applied.

Fixed

  • its dokploy env set no longer silently fails to reach Swarm containers.
    Root cause was a Dokploy 0.29.x Docker Swarm convergence bug: saveEnvironment
    persisted correctly but an in-place service.update rolled back to the
    creation-time spec, so vars added after creation never reached the container
    (Dokploy issues #4232 / #2150). The new --deploy / apply-env recreate path
    is the reliable apply route, and env-runtime --diff makes the drift visible.

Security

  • Env writes now reject redaction-masked values. saveEnvironment and the
    shared-env writer refuse any value of *** (the display mask), preventing the
    footgun where pasting redacted env/environments env output back into a
    push/set overwrites real secrets.