proxnix-workstation 0.6.1

Workstation CLI and TUI tooling for proxnix relay-cache publishing and secrets management

proxnix-workstation

proxnix-workstation packages the workstation-side proxnix tools as a normal Python distribution that can be published to PyPI and installed with pip.

It requires Python 3.12 or newer.

It installs these user-facing commands:

• proxnix
• proxnix-secrets
• proxnix-publish
• proxnix-doctor
• proxnix-tui
• proxnix-lxc-exercise

proxnix is the preferred entrypoint. The split commands remain available as compatibility aliases.

Layout

workstation/cli/
├── bin/           repo-local command wrappers for development
├── legacy/        shell-era compatibility helpers
├── src/           publishable Python package source
├── tests/         Python tests
├── pyproject.toml
└── uv.lock

If you are working from the repository rather than an installed package, use the wrappers under workstation/cli/bin/.

Generated local-only paths:

• ../.venv/ for the repo-local development virtualenv
• ../../dist/ for release artifacts
• ../../.tmp-workstation-packaging/ for packaging scratch space

Install

pip install proxnix-workstation

That installs both the workstation CLI and the terminal UI:

• proxnix
• proxnix-tui

The split commands remain available too:

• proxnix-publish
• proxnix-secrets
• proxnix-doctor
• proxnix-lxc-exercise

Or with the repo helper:

./ci/install-workstation.sh

If you want repo-local tooling instead of touching the global Python environment:

./ci/bootstrap-workstation-venv.sh

That prepares workstation/.venv plus the wrappers under workstation/cli/bin/.

Python dependencies are bundled through the package, but these external tools must still be available on the machine:

• sops
• ssh
• rsync

The commands read the same workstation config as the existing shell-based workflow:

~/.config/proxnix/config

Expected settings include:

• PROXNIX_SITE_DIR
• PROXNIX_HOSTS
• PROXNIX_SSH_IDENTITY (optional)

For source-secret retrieval, the workstation also supports:

• PROXNIX_SECRET_PROVIDER
• PROXNIX_SECRET_PROVIDER_COMMAND when PROXNIX_SECRET_PROVIDER=exec
• PROXNIX_SOPS_MASTER_IDENTITY when using embedded-sops

Secret Providers

Runtime publish artifacts always stay SOPS-based. The configurable part is the workstation source-secret backend used by proxnix-secrets, proxnix-publish, and proxnix-doctor.

Built-in provider names:

• embedded-sops
• pass
• gopass
• passhole
• pykeepass
• onepassword
• onepassword-cli
• bitwarden
• bitwarden-cli
• keepassxc
• exec

Example:

export PROXNIX_SECRET_PROVIDER=passhole
export PROXNIX_PASSHOLE_DATABASE=~/.local/share/passhole/proxnix.kdbx
export PROXNIX_PASSHOLE_PASSWORD_FILE=~/.config/proxnix/passhole-password

For passhole, proxnix asks ph to keep the database password cached for 10 minutes by default. Override with PROXNIX_PASSHOLE_CACHE_TIMEOUT or disable with PROXNIX_PASSHOLE_NO_CACHE=1.

Or:

# ~/.config/proxnix/config
PROXNIX_SECRET_PROVIDER='pykeepass'
PROXNIX_PYKEEPASS_DATABASE='~/.local/share/keepass/proxnix.kdbx'
PROXNIX_PYKEEPASS_KEYFILE='~/.config/proxnix/proxnix.keyx'
PROXNIX_PYKEEPASS_AGENT_PUBLIC_KEY='ssh-ed25519 AAAA...'
PROXNIX_PYKEEPASS_AGENT_SOCKET='~/Library/Containers/.../agent.sock'

Or:

# ~/.config/proxnix/config
PROXNIX_SECRET_PROVIDER='onepassword'
PROXNIX_1PASSWORD_VAULT='Engineering'
OP_SERVICE_ACCOUNT_TOKEN='ops_...'

Or:

# ~/.config/proxnix/config
PROXNIX_SECRET_PROVIDER='bitwarden'
PROXNIX_BITWARDEN_ORGANIZATION_ID='00000000-0000-0000-0000-000000000000'
PROXNIX_BITWARDEN_ACCESS_TOKEN='0.secret_access_token'

Those same provider variables can also be written directly into ~/.config/proxnix/config. That is the preferred place for stable proxnix provider settings.

For providers that have both SDK and CLI implementations, proxnix uses one canonical provider name for the SDK and the same name plus -cli for the CLI variant:

• onepassword and onepassword-cli
• bitwarden and bitwarden-cli

For pykeepass, the recommended setup is a static keyfile on disk plus an optional password derived from an SSH agent signature. You can print the exact derived password that proxnix will use with:

proxnix-secrets print-keepass-password

This is intended as a bootstrap/recovery path so you can also save the password in a separate personal vault and open the proxnix database directly in KeePassXC or Strongbox.

For pykeepass, the password source is chosen in this order:

1. PROXNIX_PYKEEPASS_NO_PASSWORD=1
2. PROXNIX_PYKEEPASS_PASSWORD
3. PROXNIX_PYKEEPASS_PASSWORD_FILE
4. PROXNIX_PYKEEPASS_AGENT_PUBLIC_KEY
5. no password

Those password modes are mutually exclusive in practice. PROXNIX_PYKEEPASS_KEYFILE is separate and can be combined with any of them.

If your SSH agent is not exposed through the standard SSH_AUTH_SOCK, set PROXNIX_PYKEEPASS_AGENT_SOCKET in the proxnix config file so proxnix can talk to the right socket explicitly.

Agent-derived pykeepass passwords are cached locally for 10 minutes by default so repeated GUI operations do not keep asking the SSH agent to sign. Override with PROXNIX_PYKEEPASS_CACHE_TIMEOUT or disable with PROXNIX_PYKEEPASS_NO_CACHE=1.

Examples

proxnix secrets set 120 db_password
proxnix publish
proxnix doctor --site-only
proxnix tui
proxnix exercise lxc --host root@node1 --base-vmid 940

Build

Build source and wheel distributions from the workstation/ directory:

uv build

Artifacts are written to:

workstation/dist/

Publish

Tagged releases publish the package from GitHub Actions.

For a local manual publish to PyPI:

python3 -m pip install --user --upgrade twine
python3 -m twine upload dist/*

Notes

• The package intentionally keeps sops, ssh, and rsync as external system tools.
• Some optional secret providers also require their own external tools or Python packages. For example, keepassxc, onepassword-cli, and bitwarden-cli expect their respective CLIs to be installed, while pykeepass expects the pykeepass Python package to be available and SDK-backed providers expect their Python packages plus SDK authentication: onepassword expects onepassword-sdk, and bitwarden expects bitwarden-sdk.
• Secret-store mutation and SSH key handling are implemented in Python, with sops retained at the encryption boundary for wire-format compatibility.
• Release tags are expected to match [project].version in pyproject.toml.
• Proxnix Manager is the Electrobun GUI and ships separately from a Homebrew tap; see ../docs/operations/proxnix-manager.md.
• proxnix-manager-web is the hosted Bun web server package for Nix/NixOS deployments; see ../docs/operations/proxnix-manager-web.md.