Downloads
Releases come from the GitHub releases page. Every release is built from the same commit for both editions, and the free edition tarballs are attached to the release directly:
| Platform | Free edition asset |
|---|---|
| Linux x86_64 | entwurfswerk-<version>-x86_64-unknown-linux-gnu-free.tar.gz |
| Linux aarch64 | entwurfswerk-<version>-aarch64-unknown-linux-gnu-free.tar.gz |
| macOS arm64 | entwurfswerk-<version>-aarch64-apple-darwin-free.tar.gz |
Pro artifacts are not published there: a Pro build is a different binary with a licensing gate, so it travels through its own channel. The free tarballs are complete applications; nothing in them is disabled at runtime.
Running a release
tar -xzf entwurfswerk-<version>-<target>-free.tar.gz
_build/prod/rel/<release>/bin/<release> start
Then open http://localhost:4000.
rel/env.sh.eex supplies what the release needs to boot without extra setup:
DATABASE_PATHdefaults to$ENTWURFSWERK_HOME/entwurfswerk.db($HOME/.entwurfswerk)SECRET_KEY_BASEandTOKEN_SIGNING_SECRETare generated on first start into$ENTWURFSWERK_HOME/secrets.env, outside the database- the HTTP endpoint serves by default;
ENTWURFSWERK_SERVER=0boots without it
Every value can be overridden from the environment.