appregistry

Serves the CS3 app registry on top of the service registry.

Package
github.com/cs3org/reva/v3/internal/grpc/services/appregistry
Source
internal/grpc/services/appregistry · Go reference

Enable it

Add this table to the revad configuration file:

[grpc.services.appregistry]
# settings below

Overview

Package appregistry serves the CS3 app registry on top of the service registry.

App providers do not register themselves with the app registry: they are ordinary reva services, so the runtime already advertises them in the service registry with a reachable address and a liveness state, and they describe the app they serve in their node metadata. This registry only reads that, which means an app disappears when its providers die and comes back when they return, with no registration handshake to get lost across a restart.

What it does own is the mime type catalogue: how a mime type is presented to the user, and which app opens it by default. That is deployment policy rather than something an app provider can know about itself, so it stays in the configuration.

Configuration

config

KeyTypeDefaultDescription
mime_types[]*mimeTypeConfig-MimeTypes is the catalogue: how each mime type is presented to the user and which app opens it by default. The apps themselves are discovered in the service registry, not configured. source

mimeTypeConfig

KeyTypeDefaultDescription
mime_typestring-source
extensionstring-source
namestring-source
descriptionstring-source
iconstring-source
default_appstring-source
allow_creationbool-source