Skip to content

Option to disable parts of the backend  #65

Description

@Draculente

As an admin I may want to run a microservice infrastructure. To support this without mayor engineer effort we could add the option to disable parts of the backend via envs.
With this setup one could run e.g. the feed-parser and garbage collector on one instance and the api on an other instance, or even potentially multiple other instances.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions