cookiecutter-zope-instance
  • GitHub
/

Documentation

  • Tutorials
    • Your first Zope instance
    • Docker deployment
  • How-to guides
    • Set the listen host and port
    • Configure direct filestorage
    • Configure RelStorage with PostgreSQL
    • Configure PGJsonb storage
    • Configure ZEO client
    • Configure S3 blob storage (z3blobs)
    • Configure CORS for REST API access
    • Configure logging
    • Set add-on product configuration
    • Run behind a reverse proxy
    • Use environment variables for configuration
    • Enable debug mode and profiling
    • Pack and garbage-collect the database
    • Back up and restore
    • Migrate data between storage backends
    • Upgrade from version 1 to version 2
  • Reference
    • Base locations
    • Basic configuration
    • Sample configurations
    • Logging
    • Initial user
    • ZCML
    • Database: common settings
    • Database: blob settings
    • Database: direct filestorage
    • Database: RelStorage
    • Database: ZEO
    • Database: PGJsonb
    • Database: S3 blob wrapper (z3blobs)
    • CORS
    • Development
    • Helpers
    • Changelog
  • Explanation
    • Understanding storage backends
    • How blob storage works
    • The configuration workflow
    • Why Cookiecutter for Zope configuration?
  • Glossary
  1. cookiecutter-zope-instance /
  2. Explanation

Explanation¶

Background knowledge and design decisions.

  • Understanding storage backends – Comparison of the storage backends and their trade-offs.

  • How blob storage works – How blobs are stored and cached across backends.

  • The configuration workflow – How a YAML file becomes a running instance, and why the containerized workflow is shaped the way it is.

  • Why Cookiecutter for Zope configuration? – Why this project generates configuration with a cookiecutter template.

Previous
Changelog
Next
Understanding storage backends

2022-2026, Plone Foundation

Made with Sphinx and Shibuya theme.