- Add separated Docker Compose architecture (astro/infrastructure/override) - Implement Directus + PostgreSQL with pinned versions (10.12.0/15.5-alpine) - Add comprehensive database safety protections and backup scripts - Configure production-ready NGINX reverse proxy setup - Add container names, labels, and enhanced healthchecks - Remove fallback environment variables for explicit production config - Include log rotation and monitoring improvements Infrastructure deployment: - npm run docker:infrastructure:up (one-time setup) - npm run docker:astro:up (regular deployments) - npm run db:backup/restore/status (database management) 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
30 lines
884 B
Plaintext
30 lines
884 B
Plaintext
# Directus Extensions Directory
|
|
|
|
This directory is for version-controlled Directus extensions.
|
|
|
|
## Usage Options:
|
|
|
|
### Option 1: Volume Mount (Current)
|
|
- Extensions are stored in Docker volume
|
|
- Persist through container restarts
|
|
- Not version controlled
|
|
|
|
### Option 2: Bind Mount (Version Controlled)
|
|
- Change docker-compose.infrastructure.yml to:
|
|
```yaml
|
|
- ./directus/extensions:/directus/extensions
|
|
```
|
|
- Extensions are version controlled in this directory
|
|
- Deployed with your application code
|
|
|
|
## Directory Structure:
|
|
```
|
|
directus/extensions/
|
|
├── hooks/ # Server-side hooks
|
|
├── endpoints/ # Custom API endpoints
|
|
├── interfaces/ # Admin panel interfaces
|
|
├── displays/ # Field display components
|
|
└── modules/ # Admin panel modules
|
|
```
|
|
|
|
For production, consider Option 2 to version control your custom extensions. |