|
ci/woodpecker/push/woodpecker Pipeline failed
Details
|
||
|---|---|---|
| docker/postiz | ||
| .woodpecker.yml | ||
| README.md | ||
| docker-compose.production.yml | ||
| docker-compose.staging.yml | ||
| stack.production.yml | ||
| stack.staging.yml | ||
README.md
Postiz
Deployment
This project uses Woodpecker CI for continuous integration and deployment to staging and production environments.
Woodpecker CI Configuration
The .woodpecker.yml file defines the CI/CD pipeline with the following steps:
- Building and pushing Docker images for staging
- Deploying to staging environment
- Cleaning up staging environment
- Building and pushing Docker images for production
- Deploying to production environment
Required Secrets
The following secrets need to be configured in your Woodpecker CI instance:
Registry and Docker Hub Access
REGISTRY_USER- Registry usernameREGISTRY_PASSWORD- Registry passwordDOCKER_REGISTRY_USER- Docker Hub usernameDOCKER_REGISTRY_PASSWORD- Docker Hub password
Production Environment Variables
The following secrets are injected into the stack.production.yml file during deployment:
PROD_POSTGRES_PASSWORD- PostgreSQL database passwordPROD_POSTGRES_USER- PostgreSQL usernamePROD_POSTGRES_DB- PostgreSQL database namePROD_JWT_SECRET- Secret key for JWT token generationPROD_MAIN_URL- Main application URLPROD_FRONTEND_URL- Frontend URLPROD_NEXT_PUBLIC_BACKEND_URL- Backend URL for public accessPROD_LINKEDIN_CLIENT_ID- LinkedIn OAuth client IDPROD_LINKEDIN_CLIENT_SECRET- LinkedIn OAuth client secret
Development
To run the application locally:
docker compose up --build