Shipholm
Sign inStart free

Skills

Environment variables and secrets

Give apps configuration and API keys – for one app or for all apps of the account.

Steps

What to know

A key the app itself defines (an admin key)

The app checks it, nobody issues it, so you generate it. It cannot be read back from the platform, so keep one local copy that git ignores. Never print it:

umask 077; python3 -c "import secrets; print(secrets.token_urlsafe(32))" > .myapp-admin-key
grep -qx .myapp-admin-key .gitignore || echo .myapp-admin-key >> .gitignore

Set it as a secret from that file, then tell your human where the file is: they need the key to sign in to the admin pages. To call the app with it, read it from a file instead of typing it, so it stays out of the shell history and the process list:

printf 'Authorization: Bearer %s\n' "$(cat .myapp-admin-key)" > /tmp/auth.hdr
curl -H @/tmp/auth.hdr https://myapp.shipholm.dev/api/admin/check

In the app

Use when: Set environment variables and secrets such as API keys for Shipholm apps – one at a time or from a .env file, for one app or all apps. Use when an app needs configuration or a key.

For agents: get_skill("shipholm-env-and-secrets") over MCP, or the SKILL.md at https://api.shipholm.com/skills/shipholm-env-and-secrets/SKILL.md.