| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Each instance can run a continuum of its own, pkgs.continuum by default.
|
| |
|
|
|
|
|
|
| |
An instance with a domain gets an nginx virtual host passing requests on
to its HTTP API, over a Unix socket in its runtime directory. The socket
is the instance's group's (continuum-<name>, made for it), which nginx's
user joins; continuum makes it 0660, and the directory is 0750. The
instance checks who users are itself, so requests pass on as they come.
|
| |
|
|
| |
An instance runs as a dynamic user unless it names one.
|
| |
|
|
|
|
|
| |
credentials maps names to secret files. They reach the instance by
LoadCredential, so settings refer to them as
${env:CREDENTIALS_DIRECTORY}/<name>, and the instance restarts when one
changes.
|
| |
|
|
|
|
|
|
| |
state-file and document-file, and where they apply store-file,
store-vote-record and tor.state-dir, default to files in
${env:STATE_DIRECTORY}. The defaults go in when the file is written
rather than through the module system: a default that depends on other
settings of the same free-form set recurses infinitely there.
|
|
|
hrm.continuum.instances.<name> makes a service continuum-<name> from
settings, which are continuum's options, written as TOML into the store.
The service runs as a dynamic user with a state directory and nothing
but the network. It restarts always, as continuum exits with status 0
when a transport stops.
|