collective.regenv 1.0.0a2

Features

Using this product you can:

1. have different values for development and production environments (think about the MailHost settings, connection parameters to external services, etc.)

2. have different values for different instances in the same buildout, allowing for example to toggle features on and off for A/B testing.

Documentation

Registry overrides should be in a YAML file:

% cat sample.yaml

defaults: &defaults
    plone.cachepurging.interfaces.ICachePurgingSettings.cachingProxies:
        - http://localhost:8000
        - http://localhost:8001
    plone.app.theming.interfaces.IThemeSettings.hostnameBlacklist:
        - 127.0.0.1
        - localhost

/Plone/portal_registry:
    <<: *defaults

/Plone2/portal_registry:
    <<: *defaults
    plone.cachepurging.interfaces.ICachePurgingSettings.cachingProxies:
        - http://localhost:9000

Run zope instance with environment pointing to the YAML file, for example:

PLONE_REGISTRY_YAML=$(pwd)/sample.yaml bin/instance fg

Or using the docker image, for example:

docker run -p 8080:8080 \
    -e ADDONS=collective.regenv \
    -e PLONE_REGISTRY_YAML=/app/registry.yaml \
    -v$(pwd)/sample.yaml:/app/registry.yaml \
    plone/plone-backend:latest

Installation

Install collective.regenv by adding it to your buildout:

[buildout]

...

eggs =
    collective.regenv

and then running bin/buildout

Contribute

• Issue Tracker: https://github.com/collective/collective.regenv/issues

• Source Code: https://github.com/collective/collective.regenv

• Documentation: https://pypi-hypernode.com/project/collective.regenv/

License

The project is licensed under the GPLv2.

1.0.0a2 (2022-12-27)

• Fix monkeys init [mamico]

1.0.0a1 (2022-12-27)

• Initial release. [mamico]