docs: update README - keep worker, use Blocks for flow secrets

This commit is contained in:
2026-01-31 15:08:29 +00:00
parent 115a690d8f
commit 6fa6ba5496

View File

@@ -79,10 +79,15 @@ Once deployed: https://prefect.taila5ad8.ts.net
| `redis` | Messaging broker | `redis:7-alpine` | | `redis` | Messaging broker | `redis:7-alpine` |
| `prefect-server` | API + UI | `prefecthq/prefect:3-latest` | | `prefect-server` | API + UI | `prefecthq/prefect:3-latest` |
| `prefect-services` | Background services | `prefecthq/prefect:3-latest` | | `prefect-services` | Background services | `prefecthq/prefect:3-latest` |
| `prefect-worker-pg-backup` | Worker for PostgreSQL backups | `gitea.arnodo.fr/damien/prefect-worker-pg-backup` |
## Workers & Secrets ## Work Pools
Workers are deployed separately with their own docker-compose. Flow-specific secrets (S3 credentials, API keys, etc.) should be managed via **Prefect Blocks**, not environment variables. The `prefect-worker-pg-backup` service automatically creates and listens to the `pg-backup-pool` work pool (type: process).
## Secrets Management
Flow-specific secrets (S3 credentials, database passwords, API keys, etc.) should be managed via **Prefect Blocks**, not environment variables in the compose file.
### Creating a Block (example with S3/Garage) ### Creating a Block (example with S3/Garage)
@@ -107,6 +112,11 @@ from prefect_aws import AwsCredentials
def my_backup_flow(): def my_backup_flow():
creds = AwsCredentials.load("garage-credentials") creds = AwsCredentials.load("garage-credentials")
# use creds... # use creds...
my_backup_flow.deploy(
name="my-backup",
work_pool_name="pg-backup-pool"
)
``` ```
## Repository Structure ## Repository Structure