<service>.<apps-base>. See Custom domains.
Archived service. A service removed from a project, whose metrics, deploy history and
logs stay readable. See Archived services.
Build inputs. The fields hashed into a build’s image tag: rootDir, dockerfilePath,
dockerTarget, buildArgs and the service’s env. Identical inputs on the same commit reuse the
cached image.
Build machine. The CPU and memory a project’s builds run on. See
Build machine.
Source. One slipway.yaml — a repository (or image) at a branch, and the services
that file declares. A project’s services can come from more than one source.
Cutover. The moment a public URL starts serving a new build.
Deployment. One attempt to bring a commit live, with a status, an event log and a map of
public URLs. See How deploys work.
Disk. Persistent storage attached to exactly one service. See Disks.
Environment variable. A value injected into a container at startup. In slipway, set as a
literal in the spec or as a variable or secret.
Instance. Not slipway vocabulary. What other platforms call an instance is a
service here, and what they call an instance type is a
CPU and memory allocation.
Mount path. The absolute path inside a container where a disk appears. Only data written
under it persists.
Organization. Your tenancy boundary, anchored to exactly one GitHub App installation or
GitLab group. See How it works.
Preview. A temporary copy of a project, or of one service, brought up for a pull request.
See PR previews.
Private network. The per-project network every one of a project’s services shares. See
Service to service.
Probe. A startup, readiness or liveness check declared in healthcheck:. One of http,
tcp, exec or grpc.
Project. The unit that runs: one or more services deploying together into one isolated
space, sharing config and a network. See Projects.
Provisioned size. The capacity reserved for a disk, which is what you are billed for, as
opposed to the bytes actually written.
Public port. A port marked public: true, which gives its service a hostname at the
edge. At most one per service.
Replica. One pod of a service. Every replica runs the same image with the same
configuration. See Scaling.
Resolution. Expanding every ${secret.*}, ${var.*} and ${service.*} reference to a
value at deploy time. An unresolvable secret or variable reference warns in the deploy log
and leaves the key unset; a managed database’s missing password secret, the compose
required form ${NAME:?}, and unresolvable ${service.*} references still fail the
deploy.
Rollback. Re-shipping a previous deployment’s frozen images and spec, with no rebuild.
See Rollback.
Seed default. The snapshot a cloned project’s disk is created from. Never pruned by
retention.
Service. One entry under services:, of type web, worker, cron or static. See
Service types.
Service reference. A ${service.X.field} expression, resolved at deploy time in env
and buildArgs only.
Sibling. Another service in the same project, reachable by bare name.
Sleep. Scaling a web service to zero on idle, waking it on the next request. See
Sleep on idle.
Snapshot. A point-in-time copy of a disk, restorable in place or usable to seed a clone.
Spec. The slipway.yaml describing a repository’s services. See
Overview.
Stored spec. A spec slipway holds for you, for a repository with no committed file.
Supersession. Marking a previous deployment replaced once a newer one is healthy.
Tracked branch. The branch a source deploys from.
Wakeable. A service that can be brought back from sleep, which requires it to receive
HTTP. Only a web service with a public port qualifies.