Skip to content

Feature: Set NC_serverid per instance #848

@pschichtel

Description

@pschichtel

Description of the change

Since NC 33 the UI recommends setting NC_serverid to a unique value per server of a nextcloud cluster. Since the ids should be stable and unique it suggests using a StatefulSet and using its ordinal as the serverid value.

Docs: https://docs.nextcloud.com/server/33/admin_manual/configuration_server/config_sample_php_parameters.html#serverid

Benefits

Not sure what the actual benefit is, but since NC suggests/recommends it, I guess the chart should comply.

Possible drawbacks

No idea if setting NC_serverid has drawbacks, but switching to a StatefulSet does make things a little more complicated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    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