Carsten
64dda9cb04
Burrito keys its on-host install directory on `{release}_erts-{ertsver}_{appver}`
and skips extraction when `_metadata.json` is already present for that version.
With a static `@version "0.1.0"` in mix.exs, every new build landed in the same
cached dir on the target host — silently running stale code.
Now @version resolves to `0.1.0+<BUILD_ID>` where BUILD_ID is the git short SHA
(or `dev-<timestamp>` fallback). scripts/build-linux.sh computes it on the host
and passes it through Dockerfile.build's ARG/ENV, so every commit produces a
distinct Burrito install dir and fresh extraction is guaranteed.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| config | ||
| docs | ||
| lib | ||
| rel | ||
| scripts | ||
| test | ||
| .formatter.exs | ||
| .gitignore | ||
| Dockerfile.build | ||
| mix.exs | ||
| mix.lock | ||
| README.md | ||
ProxmoxAgent
TODO: Add description
Installation
If available in Hex, the package can be installed
by adding agent to your list of dependencies in mix.exs:
def deps do
[
{:agent, "~> 0.1.0"}
]
end
Documentation can be generated with ExDoc and published on HexDocs. Once published, the docs can be found at https://hexdocs.pm/agent.