# DeployAlly

Automated deployment platform for containerized applications. Describe what you want to run in a declarative file, run one command, and get healthy containers in production — with TLS, healthchecks, dependencies resolved, and secrets generated.

# Overview

# What DeployAlly is

DeployAlly solves three problems at the same time:

• Curated template catalog: every service (database, app, proxy) is declared in a versioned, tested, and published template.
• Declarative deploy: the CLI reads the template, runs an input wizard, generates secrets, resolves dependencies (database, cache), and brings up the containers.
• Asset auto-provision: if your app needs MySQL and none is running, DeployAlly brings one up automatically — no manual orchestration required.

# How It Works

┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│   Template  │ ──▶ │   Wizard    │ ──▶ │   Deploy    │
│   (YAML)    │     │  (inputs +  │     │ (containers │
│             │     │  secrets)   │     │  + Traefik) │
└─────────────┘     └─────────────┘     └──────┬──────┘
                                               │
                                        ┌──────▼──────┐
                                        │ Auto-prov.  │
                                        │ of assets   │
                                        └─────────────┘

1. Template: declares image, inputs, secrets, HTTP routes, healthcheck, storage, and dependencies (needs).
2. Wizard: only asks what's missing (domain, admin email, etc.) and generates the rest (hex passwords, UUID tokens).
3. Deploy: applies archetype defaults, resolves Reflang references (${input.X}, ${secrets.X}, ${needs.X}), brings up containers, registers Traefik labels, and waits for healthy state.
4. Auto-provision: if the app declares needs: [{ class: mysql, ... }] and no MySQL is running, the deployer brings one up automatically with --provision-missing-assets.

# Available Templates

# Applications

# Assets

# Network

# Architecture

┌─────────────────────────────────────────────────────────┐
│                       User                              │
└─────────────────────┬───────────────────────────────────┘
                      │
        ┌─────────────┴─────────────┐
        ▼                           ▼
┌───────────────┐           ┌───────────────┐
│   Dashboard   │           │   CLI         │
│   (React)     │           │   (Rust)      │
└───────┬───────┘           └───────┬───────┘
        │                           │
        └───────────┬───────────────┘
                    ▼
            ┌───────────────┐
            │   API (Flask) │
            │   + MySQL     │
            └───────┬───────┘
                    │
        ┌───────────┴───────────┐
        ▼                       ▼
┌───────────────┐       ┌───────────────┐
│   Server 1    │       │   Server N    │
│   + Docker    │       │   + Docker    │
└───────────────┘       └───────────────┘

# Components

# Quick Start

# 1. Install the CLI
curl -fsSL https://get.deployally.com/init.sh | sudo bash

# 2. Deploy an app with full automation
deployally deploy --species memos \
  --instance-uid memos-001 \
  --input WEB_HOSTNAME=memos.example.com \
  --apply

Done. The container is available at https://memos.example.com with automatic TLS.

# System Requirements

# Target Server

• Linux (Ubuntu 20.04+, Debian 11+, RHEL 8+)
• Docker 20.10+
• Traefik running (or deploy the traefik template first)
• 1 GB RAM minimum

# Local CLI

• Linux x86_64 or aarch64 (static binary, zero dependencies)

# Next Steps

1. Installation and First Deploy — install the CLI and bring up memos in 5 minutes
2. Reflang Reference — full template language syntax
3. CLI Reference — all commands
4. API Integration — programmatic use (restricted)

# Useful Links

• Changelog — recent news
• Troubleshooting — common errors
• FAQ — frequently asked questions