Repository navigation
0.9.0 — 2026-10-05
Release Notes
Added
- Namespaced mode for engines whose namespaces are the app's own: an
Elasticsearch or OpenSearch index, a Kafka or Redpanda topic, a
Meilisearch or Typesense index, a Memcached or Redis key. Where the app reads a prefix beside the
address (ELASTICSEARCH_INDEX_PREFIX,REDIS_PREFIX), a namespaced
worktree is told one of its own — main's, then the worktree's name and
a short hash of it and the project,feat_x_1f3c4a__— and the
service is its data. A prefix is told, never made: nothing is recorded
or dropped, andrmsays what it leaves. Every process of a
namespaced worktree is toldPANDO_NAMESPACE, the same name. - A database in a container is set up with nobody asked: where the
app's login may not make the worktree's database, pando runs the
grant it used to print as the container's own administrator, read
from its environment (POSTGRES_USER/POSTGRES_PASSWORD,
MARIADB_ROOT_PASSWORD,MYSQL_ROOT_PASSWORD), and where the app's
env files carry no login, that administrator is the login, the one
rmthen drops as. Only a container that alone publishes the port on
this machine's loopback, with nothing else listening there, is taken
for the server, and an administrator is used only once it answers. A recipe says where with
[namespace.container_admin]andrun_sql. - The setup brief's first run answers
namespacedwheninitsays a
service would stay on main's data. - A server in a container is reached through the client its image
ships: when the host has nopsql,mariadborredis-cliand a
container publishes the server's port, the recipe's commands run in it
throughdocker exec, the password passed by name. namespaced, the twelfth answerinit --answerstakes: per service,
the recipe its engine is, the keys its app names its database or slot
by, and the keys it reads a prefix from, written to
[namespaced.<service>]in pando's own file beside any login. Only a
program answers it; nothing asks a person.signalslists what a
namespaced start would do with every service, an undeclared compose
service included, and why one stays shared.[namespaced.<service>] recipeandprefix_env, besidedb_env; none
is a secret, so a committedpando.tomlmay carry them.- A recipe may say only how a server somebody else runs is namespaced: a
[namespace]or[prefix]with no[service], for an engine only a
compose file runs.
Changed
- Where an app names its database or slot is a recipe's
[namespace.address]— a URL's path and query parameters, and the
keys beside the address — rather than code; a recipe without one means
its kind's conventions, as before. Every address key's own slot key is
now found: two Redis roles with their own_DBkeys both move to the
worktree's slot, where the second went on naming main's. - A slot's
sizeprints a bare number; Redis's recipe passes--raw.
Install pando-cli 0.9.0
Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mertkaradayi/pando/releases/download/v0.9.0/pando-cli-installer.sh | shInstall prebuilt binaries via Homebrew
brew install mertkaradayi/tap/pandoDownload pando-cli 0.9.0
| File | Platform | Checksum |
|---|---|---|
| pando-cli-aarch64-apple-darwin.tar.xz | Apple Silicon macOS | checksum |
| pando-cli-x86_64-apple-darwin.tar.xz | Intel macOS | checksum |
| pando-cli-aarch64-unknown-linux-musl.tar.xz | ARM64 MUSL Linux | checksum |
| pando-cli-x86_64-unknown-linux-musl.tar.xz | x64 MUSL Linux | checksum |
Verifying GitHub Artifact Attestations
The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:
gh attestation verify <file-path of downloaded artifact> --repo mertkaradayi/pandoYou can also download the attestation from GitHub and verify against that directly:
gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation> --repo mertkaradayi/pando