Crate monster_service 

Monster service: stat blocks, and the full text of spells and conditions, in a shared library (the SRD, imported by an admin) plus each campaign’s own. Every request needs a token from the auth service; a campaign sees the shared ones of its edition and its own, and can change only its own.

Re-exports

pub use store::MonsterStore;

Modules

admin

Errors, as responses. What whoever runs the service asks of it over HTTP. The monster service’s admin API (see [edda_server::admin]): exporting, importing and deleting a campaign’s own monsters, spells and conditions.

error

routes

The HTTP routes.

store

Persistence for monsters, in Postgres.

texts

Persistence for rules text (spells and conditions), alongside the monsters and shared and scoped the same way.

Structs

ApiDoc

The service’s OpenAPI description.

Functions

app

The service, accepting tokens that verifier vouches for, within limits (how many monsters, spells and conditions of its own a campaign may keep).

connect

Opens (creating if needed) the database and applies migrations.