The process on the machine. A control plane’s hands, with a signature on every one of them.
$ npm i @frontierjs/outpost
Every route but unsigned liveness requires a signature
One of these routes runs a shell command as the process’s user, so refuse is the default and a route opts out rather than in.
pull · deploy · stop · health-check · exec · logs · prune
The route table is read off the control plane’s own engines rather than invented here, so a verb it can ask for is a verb this answers.
The thing that touches Docker is a parameter
Which is what makes the package testable with no daemon and no network, and lets the control plane’s own drive run the REAL server over a fake machine.
It builds on the target and answers what it built
The digest comes back from the machine that produced it, so what is running is identified by content rather than by a tag someone may have moved.
The rest of the stack