Skip to content

refactor: replace Python operations tooling with Elixir - #9

Merged
arjayby merged 2 commits into
mainfrom
refactor/elixir-operations-scripts
Sep 12, 2026
Merged

arjayby merged 2 commits into
mainfrom
refactor/elixir-operations-scripts

Conversation

@arjayby

@arjayby arjayby commented Sep 12, 2026

Copy link
Copy Markdown
Owner

Staging and database operations required Python alongside the project's Elixir runtime. Replace both Python CLIs with standalone Elixir scripts, and update the documentation, Compose guidance, and CI to use them.

The scripts retain staging initialization, backups and checksum verification, isolated restore/load drills, upgrades, and the release pilot. Shared support handles private files, subprocess timeouts and cleanup, JSON, and verified local HTTPS. They require Elixir 1.18+ and Erlang/OTP 27+ without additional Mix dependencies; application verification still runs through Mix.

Validation completed locally:

  • Seven standalone script tests passed, including binary streams, process cleanup, private files, corrupt archive rejection, existing dotenv compatibility, and TLS trust/hostname checks.
  • The isolated restore drill and 12-client load check passed.
  • The full staging rehearsal passed against the existing synixir:step11 image, covering HTTPS, collaboration, database outage recovery, app replacement, restore verification, and metrics scraping.
  • Formatting and diff checks passed. Temporary databases and Docker resources were removed after validation.

@arjayby
arjayby merged commit 69f6316 into main Sep 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant