+
Skip to content

Container feature detection #656

@kegsay

Description

@kegsay

There are an increasing set of features which are:

  • not in the spec
  • required in practice for all production homeservers.

A few examples:

  • ability to delete media.
  • ability to delete rooms/history entirely.
  • change rate limits for the CS API.

It would be nice if a homeserver could "declare" that it supports this, which then runs some magic command on the container to enable/disable this in the container prior to startup (to avoid needing to SIGHUP a running container or other nonsense). If this declaration API is standardised, it would allow the same rate limit tests to work across different HSes for example, and if not, it can be easily skipped.

This has overlap with #654 which suggests a configuration format for saying which tests should be run. One can imagine that the "rate limit tests" were an MSC and hence could be opted-in to. The difference is that this needs configuration on a per-test basis, as we usually want very high rate limits in tests.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载