Animeet¶
Two projects, one set of docs. Pick the one you are working in.
-
animeet-api · Backend
Rails 8.1, Postgres, Sidekiq, Meilisearch, R2 behind Cloudflare. The catalog, the accounts, and everything the clients call.
-
animeet-web · Frontend
Nx and Next 16. Not documented here yet — when it is, it appears beside this one and the search covers both.
What is in the API docs¶
-
Start here
One pass over the whole system — the services, what talks to what, and where the boundaries are.
-
Where the data comes from
Five upstreams feed the catalog, none of them completely. What each one answers for, and what runs on which schedule.
-
What clients call
The REST surface, the GraphQL read API, and the ActionCable channels.
-
What changed
Every backend change visible to the frontend, newest first, with migration notes.
The short version¶
| Catalog | Anime and manga, imported from MAL and enriched from Shikimori, AniList, Kitsu and TMDB |
| Accounts | JWT plus OAuth against Google and Discord, with watch-lists and custom lists on top |
| Search | Ten Meilisearch indexes, rebuilt on every deploy |
| Media | Uploads to R2, mirrored catalog art, served through imgproxy behind Cloudflare |
| Admin | Backstage at /backstage, OTP-gated, carrying Sidekiq, Swagger and GraphiQL |
Reading this¶
Each page describes one subsystem and is meant to stay true — when the code changes, the page changes in the same commit. If a page disagrees with the code, the page is the bug.