Skip to content

Common configuration base #76

@soyouzpanda

Description

@soyouzpanda

Feature Request

To avoid having to declare all configuration variables again in each LaSuite projects, to avoid mistakes
and to have a common base for system administrators / packagers, I think all common fields in the
settings.py of each projects should be centralized here with some wrapper classes.

Examples of repetitions:

https://github.com/suitenumerique/docs/blob/24d58a1aa5e88402c14220e1f98a21bc96fd1986/src/backend/impress/settings.py#L78-L111

https://github.com/suitenumerique/meet/blob/ba8b3bda30e0b11ed3278c9553c44cea2cf720ac/src/backend/meet/settings.py#L75-L120

https://github.com/suitenumerique/drive/blob/3293ce526934d93efe9eedde5d43279c59d8a56f/src/backend/drive/settings.py#L70-L100

Potentials drawbacks would be to have less flexibility for developers on common fields (although, fields
could be overridden inside projects), but would increase security (as in
https://github.com/suitenumerique/conversations/blob/main/src/backend/conversations/settings.py
which does not use SecretFileValue for secret fields which could leads system administrators to store secrets
unsafely), efficiency and understanding.

Do you want to work on it through a Pull Request?
Yes

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions