Going to production

This sections covers the various aspects of running Procrastinate in production, and creating robust and reliable code based on Procrastinate.

Going to production

• Test your code that uses Procrastinate
• Make the most out of the logging system
• Deploy Procrastinate in a real environment
• Migrate the Procrastinate schema
  • The easier way, with service interruption
  • The safer way, without service interruption
• Execute multiple jobs at the same time
• Monitor Procrastinate in a real environment
  • The baseline: a smoke test
  • The administration shell
  • Error reporting
  • The administration web portal
• Limit the number of opened connections
• Set the database PG schema
• Delete finished jobs
  • Delete jobs on completion
  • Delete older jobs
    • From the CLI
    • In Python code
• Retry stalled jobs