Lightpress supports two deployment paths that map to different stages of the development lifecycle. Locally, Docker Compose orchestrates all services on your machine so you can develop and test without touching AWS. In production, CloudFormation provisions your AWS infrastructure and CodeBuild automates the build and deployment pipeline. Both paths share the same codebase and configuration conventions, so promoting from local to production is straightforward.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/reds-skywalker/Lightpress/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
Before deploying Lightpress in either environment, make sure you have the following tools installed and configured.- Local development
- AWS production
- Docker Desktop 4.x or later — required for Docker Compose
- Node.js 18 LTS or later — for the
client/frontend - Python 3.10+ — for scripts in
scripts/python/ - A
.envfile at the repository root (copy from.env.exampleand fill in your values)
Deployment paths
Docker Compose
Run all Lightpress services locally with a single
docker compose up command. Covers the Compose file structure, environment variables, log access, and image rebuilds.AWS CloudFormation
Provision your production AWS infrastructure with repeatable CloudFormation stacks. Covers template structure, the deploy command, stack parameters, updates, and rollback.
CI/CD with CodeBuild
Automate builds and deployments with
buildspec.yml and AWS CodeBuild. Covers build phases, source triggers, environment variables, and viewing build logs.Deployment pipeline flow
The production pipeline moves code from a source repository through CodeBuild and into AWS-managed infrastructure. The sequence below describes the end-to-end flow.Environment variable conventions
Lightpress uses.env files for local development. The .gitignore excludes .env from version control — never commit secrets to the repository. In production, pass environment variables through AWS CodeBuild environment variables or AWS Systems Manager Parameter Store and reference them from your CloudFormation templates.
Repository structure reference
The directories relevant to deployment are:| Path | Purpose |
|---|---|
docker-compose.yml | Defines all services for local Docker Compose development |
buildspec.yml | AWS CodeBuild build specification |
infraestructure/cloudformation/ | CloudFormation templates for AWS resource provisioning |
scripts/bash/ | Shell scripts for operational and deployment tasks |
scripts/python/ | Python scripts for automation and data tasks |
The
infraestructure/ directory name follows the original repository spelling. Use this exact path in all CLI commands and CloudFormation references.