基础设施概念# 通过工作池配置动态基础设施 Work pool configuration Work pool types View work pools Work pool status Pause and delete work pools Manage concurrency Base job template Work queues Queue priority Queue concurrency limits Precise control with priority and concurrency Next steps Learn about workers Worker types Worker options Worker status Worker logs Worker details Start a worker Configure prefetch Polling for work Install policy Additional resources Retrieve code from storage Deployment creation options Git-based storage Docker-based storage Custom Docker image Cloud-provider storage Store code locally Include or exclude files from storage Update flow code Flow code storage for deployments created with serve Deploy flows with Python When to consider flow.deploy over flow.serve Prerequisites Deploy a flow with flow.deploy Trigger a run Deploy with a schedule Use remote code storage Set default parameters Set job variables Deploy multiple flows Additional resources Define deployments with YAML Deployment actions The build action The push action The pull action Utility steps Templating options Work with multiple deployments with prefect.yaml Reuse configuration across deployments Deployment declaration reference Deployment fields Schedule fields Concurrency limit fields Work pool fields Deployment mechanics Update a deployment Next steps Build deployments via CI/CD Get started with GitHub Actions and Prefect Repository secrets Write a GitHub workflow Run a GitHub workflow Advanced example Deploy to multiple workspaces Caching build dependencies Prefect GitHub Actions Authenticate to other Docker image registries See also Override job configuration for specific deployments Job variables Override job variables on a deployment Use a prefect.yaml file Hard-coded job variables Use existing environment variables Use the .deploy() method Override job variables on a flow run Use the custom run form in the UI Use the CLI Use job variables in automations
