Deployment glossary

Term	Meaning
Alert rule	A threshold on one resource metric for one target. Firings appear in the environment; they are not sent externally. See metrics and alerts.
Base domain	A domain registered for a product, available when connecting a root hostname or subdomain. See domains.
Build	Converts repository code into a container image or static output. Prebuilt images and rollbacks skip this step. See deployments.
Build log	Output attached to a deployment’s build, streamed while building and readable afterward. See logs.
Custom domain	Your own hostname connected to services in one environment through DNS records and routes. See domains.
Default route	The required `/` route on a custom domain. It handles requests without a more specific route. See routes.
Deployment	A release of one service, recording its image or files and resolved configuration. At most one is active. See deployments.
Environment	Services and related resources grouped within a product, with their own private network. See environments.
Environment canvas	The environment view with service, database and volume nodes. Selecting a node opens its panel. See the deployment model.
Event	Lepsto’s timestamped record of an operation or resource state change. See events.
Fork	A one-time copy of environment configuration, without secrets, custom domains, data or deployment history. See environments.
Generated domain	The service’s default `lepsto.run` hostname, with a fixed route to that service. See domains.
Health check	An optional HTTP probe for readiness or liveness. See health checks.
Liveness check	A probe that restarts a running replica when it stops responding. See scaling.
Log level	`error`, `warn`, `info` or `debug`, derived from structured output or message text. See logs.
Managed database	A database operated by Lepsto, either within one environment or through Managed Postgres. See databases.
Managed Postgres	Product-level Postgres instances containing logical databases attachable across environments. See Managed Postgres.
Managed service	An environment-managed PostgreSQL, MySQL, Redis or MongoDB database with private connection variables. See databases.
Mount path	The absolute container path where a volume appears, chosen at volume creation. See volumes.
One-off command	A non-interactive command that returns output and an exit code, run in a replica or separate container. See commands.
Preview environment	A pull-request fork that redeploys on commits and expires after closure or inactivity. See previews.
Preview policy	A base environment’s settings for enabling previews, their maximum count and lifetime. See previews.
Product	The owner of deployment environments and product-level resources, including Managed Postgres. See the deployment model.
Readiness check	A probe controlling whether a replica can receive traffic and a new release can become active. See scaling.
Redeploy	A new deployment from current source and variables, without needing a new commit. See deployments.
Release	Another name for a deployment. See deployments.
Replica	One running copy of a service’s current release. Requests can reach different replicas. See scaling.
Restart	Starts the same runtime image again without a build or new deployment entry. See deployments.
Rollback	Creates a new deployment from an earlier image with current variables. See rollback.
Route	A custom-domain path prefix mapped to a service in the same environment. See routes.
Runtime log	Output a container writes to stdout/stderr. Static sites have none. See logs.
Scale to zero	Opt-in sleep after an idle window, with startup triggered by a request or explicit wake. See scaling.
Secret	An encrypted, write-only variable whose old value cannot be listed. See variables.
Separate run	A temporary container from a service’s current image and variables for a one-off command. See commands.
Service	A deployable unit with a source, settings and deployment history in one environment. See services.
Service source	Repository, image or static archive used to build or publish the service. See sources.
Service type	Runtime container or static site; the type determines sources and available settings. See services.
Slug	A short resource identifier, unique within its containing scope. Environment slugs remain fixed after creation. See environments.
Snapshot	A release’s captured source and resolved variables, or a database backup’s stored contents; the context distinguishes them. See deployments and database backups.
SSH key	A public key registered for the product so your SSH client can enter a running replica. See SSH.
Static site	Built files served without a long-running application container. See static sites.
Terminal	An interactive browser shell inside a running replica. See commands.
Variable	Named configuration inherited from product, environment and service levels. See variables.
Variable reference	`${{KEY}}` or `${{slug.KEY}}` resolved into a variable value when a deployment starts. See references.
Volume	Persistent disk mounted into one service. It survives container replacement and requires an interrupted rollout. See volumes.
Wake	Start a sleeping service on its existing release, through a request or an explicit action. See scaling.

Was this page helpful?