Applications & Git deploy
Run native or container apps, and deploy from a Git repository.
Describe the app
Create apps from the Applications page or as files under /etc/uwas/apps.d. Native runtimes include Node.js, Python, Ruby and Go; Docker and custom processes are supported too.
Configuration exampleyaml
# /etc/uwas/apps.d/my-api.yaml
name: my-api
runtime: node
work_dir: /var/lib/uwas/apps/my-api
port: 0
env:
NODE_ENV: production
# Route in uwas.yaml
domains:
- host: api.example.com
type: proxy
ssl:
mode: auto
proxy:
upstreams:
- address: "apps://my-api"
Connect Git
Persist deploy settings in the app definition or use the dashboard. When build_cmd is empty, UWAS attempts build detection. A configured health_path checks for an HTTP 2xx/3xx response after startup.
Configuration exampleyaml
deploy:
git_url: https://github.com/your-org/your-app.git
git_branch: main
health_path: /health
branch_filter: main
Private repos and deploy events
Private repositories support HTTPS tokens or SSH deploy keys. Configure a webhook secret and use the app webhook endpoint from the upstream guide. Live deploy logs stream to the dashboard. Failed deployments can reset an existing repository to its previous commit; this does not roll back external databases.
Need every option? Read the complete configuration reference and the upstream upgrade notes for your release.