Uses the mod list in mods.json of the source branch, fetches the required data for each mod. That data is then added to database.json in the master branch. The process happens automatically every once in a while.

The database is deployed to GitHub Pages, since GitHub aggressively caches direct access to the raw file in the repo. So if you want to read from the database, you should use this URL: https://ow-mods.github.io/ow-mod-db/database.json

Or, if you want, you can edit the mod list yourself and open a PR

GitHub Actions are used to periodically update the database. Check the Update Releases workflow and the TypeScript code that fetches the data about each mod and generates the database.

If you fork this repository, you'll need to add a few secrets for everything to work.

GitHub token with repo permissions. Format:

ghp_XXX

User name that owns GH_TOKEN

Discord web hook URL where all the notifications are sent. Format:

https://discord.com/api/webhooks/XXX/YYY

JSON object where keys are the uniqueName of a mod, and the values are the Discord hook urls of the channel where update notifications should be sent to. Format:

{
  "uniqueNameA": "https://discord.com/api/webhooks/XXX/YYY",
  "uniqueNameB": "https://discord.com/api/webhooks/WWW/ZZZ"
}

ID for the Discord role to ping when there's a mod update.

ID for the Discord role to ping when there's a new mod added to the database.

Base64-encoded JSON object. Credentials of a Google service account with permissions to get the outerwildsmods.com view counts from google analytics. JSON format (before base64 encoding):

{
  "type": "service_account",
  "project_id": "XXX",
  "private_key_id": "XXX",
  "private_key": "XXX",
  "client_email": "XXX",
  "client_id": "XXX",
  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
  "token_uri": "https://oauth2.googleapis.com/token",
  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
  "client_x509_cert_url": "XXX"
}