Skip to content

Move some configuration to the Pod Server #361

@RemiBardon

Description

@RemiBardon

The Pod API reads some configuration from prose.toml only to include it in the generated Prosody configuration. We should instead move that configuration to the Pod Server, which would create a partial configuration file that would be included via Include in the main Prosody configuration file.

Or we could do it the other way around: the Pod Server generates a file with Includes and the Pod API only writes those. That might be cleaner.


Note: Using Includes would also be a cleaner way to handle raw overrides, and would be more efficient as we wouldn’t have to load ALL of the configuration to regenerate parts of it. That’d make snapshot tests a bit more involved, but also more granular so I guess it’s fine.

Metadata

Metadata

Assignees

No one assigned

    Labels

    cleanupRefactors / cleans up the codeenhancementNew feature or requestneeds designFeature design must be done before work can beginsecurityRelates to security

    Type

    Projects

    Status

    Backlog & Ideas 💡

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions