Overview — Aquilia Documentation
Comprehensive guide and documentation for Overview in the Aquilia framework. View API reference, examples, and implementation patterns.
function DeploymentArchitecture() = useTheme() const isDark = theme === 'dark' return ( DIAGNOSTICS aq doctor & validate COMPILATION docker build amd64 REGISTRY PUSH docker push image RESOLUTION owner & config lookup PROVISIONING api deploy & vars sync LIVENESS POLL wait live or rollback ) } Providers Overview Cloud provider integrations, architecture, and deployment strategy Aquilia features a highly decoupled, container-first deployment pipeline. While the framework provides CLI commands to generate raw configuration files for Kubernetes, Nginx, Docker Compose, and Makefiles, it also offers first-class PaaS provider integrations, allowing developers to configure and deploy workspaces in a single command. Container-First Strategy Aquilia treats containerization as a fundamental building block, rather than an afterthought. Because the runtime is built around self-contained ASGI structures and manifest configurations, any Aquilia workspace can be packaged into an OCI-compliant container image. The framework leverages this by exposing a two-tiered deployment strategy: 1. Static Infrastructure-as-Code Generate local configs via commands like aq deploy dockerfile, aq deploy k8s, or aq deploy nginx. This allows complete portability to custom cloud clusters, VPS nodes, or in-house hardware. 2. Managed PaaS Integration Direct, API-driven deployments to managed platforms like Render. The framework introspects your active workspace features and maps them directly to cloud services, databases, cache layers, environment variables, and auto-scaling rules. Deployment Pipeline Architecture The orchestration path flows sequentially from the local workstation to the cloud provider. Here is how the pipeline connects local diagnostics, container building, registry synchronization, and API service provisioning: , , , , , , ].map((item, i) => ( ))} Configuration Approaches Aquilia supports two distinct ways to define Render integration settings in workspace.py: the Fluent API Integration and the Class-Based Configuration (Recommended). Method 1: Class-Based Config (Recommended) Defined inside the environment layering configurations inheriting from AquilaConfig. This is the recommended approach because it supports environment-specific overrides (e.g., using different machine plans or ports in dev vs. production environments) and supports twelve-factor variables via Env(). Method 2: Fluent API Integration Defined by instantiating a RenderIntegration object and passing it directly to the workspace's integrate() method. This is suitable for simpler, monolithic configurations that do not use multi-environment config layering. Next Chapters 01 Render PaaS Integration Deployment pipeline workflow details, API clients, and service configuration payloads. 02 Secure Credential Store Key derivation cryptography, encrypted credentials payload formatting, and local audit logs. 03 CLI Reference Guide Complete command flags, environment variable synchronizations, and CLI diagnostics. ) } function ArrowRightIcon() { return ( )
Go to Homepage