The application in part 4 can run without credentials, but a project using a database or external API will need them. I keep those values in 1Password and send a job the field it needs from my Mac. I approve the read locally, and the value travels over the SSH connection configured in part 2. The VPS does not need a credential that can read the whole vault. The example below uses a harmless marker to check that route before supplying an application credential.
Send a value to a job
The 1Password command-line interface, or CLI, is the op program. On the Mac, download and open the op.pkg installer from the macOS installation instructions, then enable Integrate with 1Password CLI in the app's Settings, Developer page. Keep the app unlocked. Run op --version in a local Mac terminal to check installation; it should print a version number.
The sender also uses Python 3 on the Mac. Check python3 --version; if it is unavailable, install it using the Python macOS installer and open a new terminal. The version checks should look like this, using your installed versions:
$ op --version
2.<CLI_VERSION>
$ python3 --version
Python 3.<PYTHON_VERSION>
A secret reference identifies a vault item and field:
op://Engineering/Transport check/value
Here, Engineering is an example vault, Transport check is an item and value is its field. The CLI's op read command resolves that reference. Its --no-newline option returns the value without adding a line ending. Use a separate credential for each application's needs. An application's database password should not be the VPS recovery password under a different name.
In 1Password on the Mac, create an item named Transport check in your development vault, add a text field labelled value and set it to transport-check-only. The example receiver runs a fixed container job that checks this marker and prints a success message. It accepts exactly one field, DEMO_TOKEN. Save receive-demo-job.py and send-demo-job.py in ~/Downloads/private-vps-examples on the Mac and inspect both. In a local Mac terminal, run cd ~/Downloads/private-vps-examples, then nano send-demo-job.py. Change its reference string to match your vault, item and field, treating real names as private configuration.
Still in that local Mac terminal, install the receiver under builder on the VPS. These quoted SSH commands return to the Mac after each operation:
ssh workbench 'install -d -m 700 /home/builder/.local/bin'
scp receive-demo-job.py workbench:/home/builder/.local/bin/receive-demo-job
ssh workbench 'chmod 700 /home/builder/.local/bin/receive-demo-job'
The sender runs op read on the Mac and sends the result as JSON over SSH's standard input. Its command line names the receiver without containing the retrieved value. The receiver validates the request and passes DEMO_TOKEN to a rootless container through its environment.
Run the sender on the Mac:
python3 send-demo-job.py
Approve the 1Password request. Expected output:
transport check passed
The first run can also show Docker image-download messages. The final success line should appear without printing the marker itself. If the vault read fails, the sender stops before starting a remote job; check the Mac's 1Password CLI integration and the reference you saved before retrying.
Use the pattern for an application
For an actual job, replace the fixed image and command with the application you intend to run, and define the specific environment names it may receive. The receiver rejects extra fields and limits the request size; keep those checks when adapting it. Accepting names such as DOCKER_HOST, PATH or PYTHONPATH could change the launcher itself, so a general-purpose list of uppercase names is not enough.
The same principle applies if you add a project mount. Resolve it beneath the intended projects directory, check where symlinks lead and pass commands as argument lists rather than assembling a shell command.
Sending the value through standard input keeps it out of SSH command arguments and avoids a helper-created temporary file. It still exists in process memory and in the container's environment configuration. The development account owns the Docker daemon and can inspect its containers. That includes the Amp host runner, which uses the same account. A container without a Docker socket does not hide its credentials from the daemon's owner or the host administrator.
Keep application logs free of credentials too. For a persistent service, decide how its secret will be stored or fetched at startup, including after a reboot. This one-job workflow keeps broad vault access on the Mac; it does not supply automatic secret renewal to every application.