This service allows you to create an ActivityPub server with data stored in a triple store.
- Store activities, actors and objects in the triple store
- Handle all kind of ontologies (see
- Allow to create actors when new WebIDs are created
- Currently supported activities:
Configure the LDP containers
The containers for actors and objects are handled through the LDP service. You need to define containers with ActivityStreams's actors and objects in the
acceptedTypes. Alternatively, you can load the default containers from the
@semapps/activitypub package as below:
Configure the API routes
Queue federation POSTs
If you want to make sure no data is lost when trying to POST to remote ActivityPub servers, you can set the
The Bull task manager will queue the task and you will be able to retry it if it fails.
Create actors on WebID creations
This is done automatically when a
webid.created event is detected.
|required||Base URI of your web server|
|The ActivityStreams ontology is the base ontology, but you can add more contexts here if you wish.|
|Redis connection string. If set, the Bull task manager will be used to handle federation POSTs.|
The following service actions are available:
Object - Routes formatted for the Moleculer ApiGateway