Deploying
How an agent ships an app, and what happens to it.
From the agent
supersecret_app_deploy takes the app's source as a map of file path to
content, plus a slug. Calling it again with the same slug builds a new release
rather than a second app.
The build runs with no network (APPD_BUILD_NETWORK=none). A build that
expects to download dependencies at build time will fail; vendor them, or use a
base image that already carries them.
After the build
Read supersecret_app_status. It returns:
- the link the app is served at
- the build state of the current release
- the container state
- the network map, with each connection's approval status
If the build failed, supersecret_app_logs returns the build log alongside
recent output. Read it rather than redeploying blind.
Releases
Every deploy is a release, retained with its build state and events. Rolling back selects an earlier release rather than rebuilding from older source.
Deleting an app stops its container and removes its volume and links, but releases and events stay in the audit history — you keep the record of what ran.