Konyanko

A nyaa.si aggregator.

Roadmap

• Schema with entgo
• RSS reader-exporter
• Anime name parser
• Iterative cycles of two above till completed
• OpenAPI specs from ent schema
• GraphQL schema
• API server
• Vue UI
• Templ + htmx UI
• Crontab RSS puller on server
• Goreleaser
• Docker

Maybe later

• Myanimelist integration
• Terminal UI

Schema

---
title: Konyanko schema
---
erDiagram
    Anime ||--o{ Episode : edge
    Anime {
        int    id
        string title
    }
    ReleaseGroup ||--o{ Episode : edge
    ReleaseGroup {
        int    id
        string name
    }
    Episode ||--|| Item : edge
    Episode {
        int id
        int episode_number
        int anime_season
        string resolution
        string video_codec
        string audio_codec
    }
    Item {
        int id
        string view_url
        string download_url
        string file_name
        int file_size
        datetime publish_date
    }

GraphQL specs

GraphQL schema

Dev runflow

$ make generate
$ make migrate
$ make import
$ make describe

Lessons learned

• It feels like ent doesn't really want to be ORM, but rather be a graph API.
• Generating REST with ogent OpenAPI isn't horrible, but resulting API is not really flexible and writing custom end-points is quite a hustle.
• HTMX + templ is interesting combination as an option, but it has all the negatives of REST without positive of ogent's auto-gen. Plus the workflow of "shut down server, regen templ, compile modules, start server" for anything, including tiny tweaks on css is really, really annoying.