lodestone_core VS nitro_repo

I personally use deno for the Lodestone Project, a FOSS open-source game server hosting tool (shameless plug). One of the features coming up is a plugin system that allows users to write typescript code to communicate with lodestone directly and a system that allows users to implement a game server instance in typescript which lodestone can run at runtime, all powered by deno. If you are interested the code is here and here

The project (backend for a server hosting/management panel) is using `mlua` for its user-customizable scripting feature. It was extremely (well compared to Deno) easy to set up and it does 99% of what we need, but its syntax, object model, and the lack of language-wide async support have been getting to me, so I was excited to give Deno a try.

Was starting a new project (Lodestone) that needed a web server, didn't want to use Node or typescript so I decided to give rust a try. Never looked back :D

Been grinding away at Lodestone, a self-hosted game server wrapper/management tool originally designed for Minecraft, but we are planning support for other servers such as Risk of Rain, Terraria, Genshin etc etc.

Continuing my development of 1.1 of my artifact manager nitro_repo. Trying to work more on the admin panel tho so more typescript/Vue less Rust.

Over the past few months I have been working on an open source Artifact Manger https://github.com/wherkamp/nitro_repo. Currently the only working and stable artifact type is Maven. I am wanting to add support for more. However, I am wanting to see if I can get some community interest in the project before I start on other artifact types. This is not meant to be an alternative to Nexus. This is supposed to be a Nexus for the smaller projects/groups. I wrote it in Rust using Actix Web and a Vue front end. I am relatively new to Rust and I really not sure how to go about distributing Nitro Repo.