[v3.0] Database rewrite

[Juknum]

This issue will list all the necessary steps to do before releasing the v3.0. It's mandatory since the v2 is currently sick of a mid-time remake that lacks direction, comprehension & reliability. The v3 is there to replace the v2 & definitely close the v1

• [x] Switch from firestorm to MangoDB

  • [x] Setup MangoDB server on the VPS

• [ ] Define new models for data:

  • [ ] Textures
  • [ ] Contributions
  • [ ] Changelogs
  • [ ] Posts
  • [ ] Addons
  • [ ] Website Posts
  • [ ] Mods
  • [ ] Modpacks
  • [ ] Users

• [ ] Migrate data

[3vorp]

just curious, is there any significant difference between mongodb and firestorm? both are really just collections of json files iirc lol

[TheRolfFR]

it's more professional and more performant, widely used. I coded Firestorm so yeah it will be more maintanable

[Pomi108]

Oh lol, I didn't even know Firestorm was your thing, nice

[3vorp]

ah makes sense

[Pomi108]

mfw

[3vorp]

tbh other than some minor interface problems with v2 that could pretty easily be resolved directly (stuff like splitting contributions by resolution rather than pack, some deprecated moderation stuff, etc) I've not noticed too many problems with the v2 api as a whole

[3vorp]

tbh I don't see this happening without juk at all since other than a few easily solvable singular problematic areas I see no problem with v2 and its general systems of uses/paths, so I'm gonna close this unless someone wants to pick it up again