部署

• Deploy overview
  • Create a deployment
    • Create a deployment with serve
    • Create a work pool-based deployment
    • Create a deployment with deploy
    • Create a deployment with a YAML file
    • Work pools
    • Work pool-based deployment requirements
  • Run a deployment
    • Work pools that require a worker
    • Work pools that don’t require a worker
  • Static vs. dynamic infrastructure
    • Static infrastructure
    • Dynamic infrastructure
  • Deployment schema
    • Required defining data
    • Workflow scheduling and parametrization
    • Concurrency limiting
    • Metadata for bookkeeping
    • Worker-specific fields
• Run flows in local processes
  • Serve a flow
  • Additional serve options
  • Serve multiple flows at once
  • Retrieve a flow from remote storage
  • If you need dynamic infrastructure
• 基础设施概念
  • 通过工作池配置动态基础设施
    • 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
• 基础设施示例
  • Run flows in Docker containers
    • Create a work pool
    • Start a worker
    • Create the deployment
      • Automatically bake your code into a Docker image
      • Automatically build a custom Docker image with a local Dockerfile
      • Store your code in git-based cloud storage
      • Additional configuration with .deploy
      • Work with multiple deployments with deploy
    • Learn more
  • Run flows on Kubernetes
    • Prerequisites
    • Create a cluster
    • Create a container registry
    • Create a Kubernetes work pool
      • Configure work pool options
    • Create a Prefect Cloud API key
    • Deploy a worker using Helm
      • Add the Prefect Helm repository
      • Create a namespace
      • Create a Kubernetes secret for the Prefect API key
      • Configure Helm chart values
      • Create a Helm release
      • Verify deployment
    • Define a flow
    • Define a Prefect deployment
      • Tag images with a Git SHA
    • Authenticate to Prefect
    • Deploy the flows
    • Run the flows
  • Run flows on Prefect Managed infrastructure
    • Create a managed deployment
    • Add dependencies
    • Limitations
      • Concurrency and work pools
      • Images
      • Code storage
      • Resources
    • Usage limits
    • Next steps
  • Run flows on serverless compute
    • Automatic infrastructure provisioning
      • Prerequisites
      • Automatically create a new push work pool and provision infrastructure
      • Use existing resources with automatic infrastructure provisioning
    • Provision infrastructure for an existing push work pool
    • Manual infrastructure provisioning
      • Work pool configuration
      • Create a Credentials block
      • Create a push work pool
    • Deployment
    • Putting it all together
    • Next steps
• 静态基础设施示例
  • Serve flows in a long-lived Docker container
    • Overview
    • Writing the flow
    • Writing the Dockerfile
    • Build and run the container
      • Build (and push) the image
      • Run the container
        • Verify the container is running
        • View logs
      • Stop the container
    • Next steps
• Daemonize worker processes
  • Prerequisites
  • Steps
    • Step 1: Add a user
    • Step 2: Install Prefect
    • Step 3: Set up a systemd service
      • Setting up a systemd service for a Prefect worker
      • Setting up a systemd service for .serve
    • Step 4: Save, enable, and start the service