https://github.com/eiri/konyanko

A nyaa.si aggregator
https://github.com/eiri/konyanko

Last synced: 28 days ago
JSON representation

A nyaa.si aggregator

• Host: GitHub
• URL: https://github.com/eiri/konyanko
• Owner: eiri
• Created: 2023-10-10T01:42:42.000Z (about 1 year ago)
• Default Branch: main
• Last Pushed: 2024-01-17T02:18:14.000Z (10 months ago)
• Last Synced: 2024-06-21T08:16:32.899Z (5 months ago)
• Language: Go
• Size: 639 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Konyanko

A nyaa.si aggregator.

## Roadmap

- [x] Schema with entgo

- [x] RSS reader-exporter

- [x] Anime name parser

- [x] Iterative cycles of two above till completed

- [x] ~OpenAPI specs from ent schema~

- [x] GraphQL schema

- [x] API server

- [ ] Vue UI

- [ ] ~Templ + htmx UI~

- [ ] Crontab RSS puller on server

- [ ] Goreleaser

- [ ] Docker

## Maybe later

- [ ] Myanimelist integration

- [ ] Terminal UI

## Schema

```mermaid

---

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](https://github.com/eiri/konyanko/blob/main/konyanko.graphql)

## Dev runflow

```bash

$ 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.