Yeah this makes sense, let's make a branch of the current working code, like a V01.XX.XX and generate a docker image for that so people can force their server to run that code.

And you can just merge my current json API branch into this Server V2 branch if you want a head start. Once that's done we can close my branch and Implement json API as part of V2 and not have any in V1

You want a hard cut-over? The way I wrote the current requests, we could still have both parts running, and be future-proof (v3,4,5...) too.
But yea I will merge your current branch into this one

I think something as big as an API changing structure would be enough to do a hard cut-over, it's your call in the end but I think V2 being the version with the big API change makes sense to me and then we just leave the old version alone, maybe patch it every now and then if we need to but otherwise leave it alone.

Also do you want to take the lead on the server side of V2 then? That'll let me focus on doing the frontend V2 implementing all these manga pop-up and search/add pop-up changes that everybody's been wanting. I can also then implement any other changes as a result of the server V2. What do you think?

Sounds like plan!
So it would essentially be complete V2 front- and backend, then a hard cut-over would make a lot of sense.

Hi 👋
Happy holidays!

Since I have some free time, is there a list of stuff that needs to be done to push forward either tranga or tranga-website? (Not promising anything but I'll try)

Hey @ale-ben, thanks for the offer! Happy Holidays! I think on the front end, the current pure JavaScript + CSS needs to be migrated over to the react + Typescript format.

Thanks for the reply @db-2001!
As far as I can tell, the migration to react + ts has already begun in the vite-react-ts branch. Am I wrong?

What still needs to be done?

Btw, if u want to add me on discord here's the link https://discord.gg/jS94ybbn

Hi @ale-ben !
Yes the frontend rewrite has moved to vite-react-ts.
For the most part things kind of work.
The Backend is in pg-v2 and is a postgres-database rewrite with ASP.NET Endpoints.
If you build it, a swagger doc should be generated with the endpoint-names. Functionality is not really there yet (searching works), as Entity Framework Code-First and Lazyloading are a bit of a pain to get to work correctly, but that is currently the biggest front of my workload.

Ok, thanks for the update!
I'll try cloning pg-v2 and see what happens.

Since v2 branch is pg-v2 I'll close #308

I might have lied, it is postgres-server-v2 (a merge between both attempts) ;)
https://github.com/C9Glax/tranga/tree/postgres-Server-V2

Ok, it took a while due various compilation problems but finally I got the API working!

The main problem now is that frontend refuses to communicate with the API. It keeps getting stuck here:
https://github.com/C9Glax/tranga-website/blob/0402f9e6d003601b0f6976b8638c390d38cb8e69/Website/App.tsx#L129

Frontend tries to call {apiUri}/v2/Ping but I can find no mention of this endpoint here...

Am I missing something or is this endpoint not implemented yet?