5e-srd-api

REST API to access D&D 5th Edition SRD API

Talk to us on Discord!

How to Run

Make sure you have the latest version of the database:

docker compose pull

Then run it with docker-compose:

docker compose up --build

M1/M2 Macs

The command above pulls the latest image of the database from ghcr.io, which only targets the amd64 platform. If you are running on a different platform (like an M1/M2 mac), you will need to build the image yourself. See the 5e-database repo for additional details.

cd ../
git clone https://github.com/5e-bits/5e-database.git

Then back over here in the 5e-srd-api repo, in the file docker-compose.yml, you can replace the line image: bagelbits/5e-database with build: ../5e-database (or whatever you named the custom db image).

Making API Requests

Make API requests by using the root address: http://localhost:3000/api/

You should get a response with the available endpoints for the root:

{
  "ability-scores": "/api/ability-scores",
  "classes": "/api/classes",
  "conditions": "/api/conditions",
  "damage-types": "/api/damage-types",
  "equipment-categories": "/api/equipment-categories",
  "equipment": "/api/equipment",
  "features": "/api/features",
  "languages": "/api/languages",
  "magic-schools": "/api/magic-schools",
  "monsters": "/api/monsters",
  "proficiencies": "/api/proficiencies",
  "races": "/api/races",
  "skills": "/api/skills",
  "spells": "/api/spells",
  "subclasses": "/api/subclasses",
  "subraces": "/api/subraces",
  "traits": "/api/traits",
  "weapon-properties": "/api/weapon-properties"
}

Working with a local image of 5e Database

If you are working on a feature which requires changes to both this repo, and the 5e-database repo, it is useful to know how to connect the former to the latter for testing purposes. A simple process for doing so is as follows:

1. In the file docker-compose.yml, you can replace the line image: bagelbits/5e-database with build: [relativePathToDatabaseRepo]. Make sure not to commit this change, as it is intended for local testing only.

2. Run your branch of 5e-srd-api using the method outlined in the above section of this readme file. So long as there are no transient errors, the API should build successfully, and your changes to both repos should be noticeable.

Working with image resources from s3

The API uses s3 to store image files for monsters. The image files live in a bucket called dnd-5e-api-images under the /monsters folder.

To test locally, you can use localstack to mock s3. To do so, you will first need to install localstack, awscli, and awslocal. You can then run the following commands to configure and start the localstack container:

export AWS_CONFIG_ENV=localstack_dev
localstack start
awslocal s3api create-bucket --bucket dnd-5e-api-images
awslocal s3 cp aboleth.png s3://dnd-5e-api-images/monsters/
npm run dev

Request the image by navigating to an image URL in a browser, or via HTTP request:

curl http://localhost:3000/api/monsters/aboleth.png --output downloaded-aboleth.png

When interacting with the image you should see logs in the terminal where you started localstack. You can also use localstack's webui to view the bucket and contents.

Data Issues

If you see anything wrong with the data itself, please open an issue or PR over here.

Running Tests

Unit Tests

You can run unit tests locally by using the command: npm run test:unit

Integration Tests

Integration tests need to be ran in the API docker container for them to function properly. In order to run integration tests locally you can use the command: npm run test:integration:local

Documentation

Public facing API documentation lives here.

We use RapiDoc to create the documentation UI from a bundled single file OpenAPI definition created as part of the npm run build task.

Additional details and information on working with the documentation can be found in the /swagger directory's README.

Contributing

• Fork this repository
• Create a new branch for your work
• Push up any changes to your branch, and open a pull request. Don't feel it needs to be perfect — incomplete work is totally fine. We'd love to help get it ready for merging.

Code of Conduct

The Code of Conduct for this repo can be found here.

Contributors