About
Release-gated continuous delivery: follows a registry image channel and redeploys the product safely, with backup, health check and rollback
Provides
AutodeployService
/admin/deployments/admin/deployments/check/admin/deployments/pause/admin/deployments/resume
layout.authenticated_sidebar
es
Commands
-
$
splent feature:autodeploy checkAsk the agent to look for a new release now.
-
$
splent feature:autodeploy history [OPTIONS]The latest deploys, newest first.
-
$
splent feature:autodeploy pauseStop automatic deploys until resumed. A deploy in progress finishes.
-
$
splent feature:autodeploy resumeTurn automatic deploys back on, and check right away.
-
$
splent feature:autodeploy status [OPTIONS]What the deployment agent is doing and what the product runs.
Run them in your workspace once the feature is installed in the selected product.
Configuration
| Setting | Default | What it does |
|---|---|---|
AUTODEPLOY_IMAGE |
empty | The registry image to follow. Empty means SPLENT_IMAGE, the image the web service runs, which is the usual choice: the server follows the channel it was deployed from, git.splent.io/splent-io/<product>:stable for example, and that tag only moves when someone runs splent product:release. Never :latest, which the agent refuses; the container it creates runs the image's digest, whatever tag it followed. |
AUTODEPLOY_INTERVAL |
300
|
Seconds between two looks at the registry. A pull of an image already present costs one manifest request. |
AUTODEPLOY_WINDOW |
empty | Daily UTC span in which a deploy may start, like 02:00-05:00. It may wrap past midnight (22:00-04:00). Empty means any time. |
AUTODEPLOY_URL |
http://<product>_autodeploy:8080
|
Where the web side finds the agent's API, on the product network. |
AUTODEPLOY_SECRET |
Required | Shared by the web container and the agent; every API call carries it. product:deploy offers a random value for it. Has no default, so the product must set a value. |
These are the defaults. A product changes them in its own pyproject.toml, under [tool.splent.config], or in .env.deploy in production. <product> stands for the name of the product that takes the feature.
Services and ports
splent_feature_autodeploy
autodeploy_data
docker-compose.prod.yml
They start with the product. Host ports come from variables, so two products on one machine never collide.
Dependencies
In product lines
-
cms_spl
Optional in this line
Needs
admin -
marketplace_spl
Optional in this line
Needs
admin -
openhubs_spl
Optional in this line
Needs
adminauth -
openwiki_spl
Optional in this line
Needs
admin
Extension points
autodeploy/index.htmlhooks/sidebar_deployments.html
AutodeployService
Other features fill its hook slots. A refinement can override its templates and services or extend its models without forking it.
Compatibility
>=3.13
>=1.30.0