gfargo/strut Deploy

Deploy Docker stacks to a VPS using strut — SSH key + env handled securely, one step replaces the full release pipeline

Trust Signals

name	description	required	default
stack	Stack name — must match a subdirectory under stacks/ in your project	yes	—
command	strut command to run: release (recommended for CI), ship, health, or deploy (self-hosted only)	no	release
env	Environment name — resolves to .<env>.env in the project root (e.g. prod → .prod.env)	no	prod
services	Services profile passed as --services <profile> (optional)	no	""
strict	Pass --strict to release — treat migration failures as fatal	no	false
dry-run	Pass --dry-run — print the execution plan without making changes	no	false
version	strut tag to install (e.g. v0.30.4). Pin to a release tag for reproducible deploys.	no	main
host	VPS hostname or IP address (sets VPS_HOST) — pass as a repository secret	yes	—
ssh-key	Private SSH key contents for VPS access (sets VPS_SSH_KEY) — pass as a repository secret	yes	—
ssh-port	SSH port on the VPS (sets VPS_PORT)	no	22
user	SSH user on the VPS (sets VPS_USER)	no	ubuntu
deploy-dir	Deployment directory on the VPS (sets VPS_DEPLOY_DIR). Defaults to /home/<user>/strut	no	""
env-vars	Extra environment variables as newline-separated KEY=VALUE pairs (e.g. GH_PAT, REGISTRY_TOKEN)	no	""

no outputs