Serious questions: if I were to migrate Sonic Worlds Next's primary git repository off GitHub to elsewhere...
1.) Would I lose the Discussions feature and its archive of messages? I intentionally enabled it on the repo to create a message board for users to discuss utilizing the project, in lieu of abusing the bug tracker for non-bugs, and I'm not sure if Codeberg or Forgejo support that feature. I won't be nuking the GitHub repo, but being able to continue using this forum on where development is active is kinda important!
2.) How good are the Discord integration features of Codeberg or Forgejo? We (the Worlds Next Team) use a private Discord server for discussing internal matters and have a channel for monitoring all repo activity, and it would be rad if we can keep using existing infrastructure.
The main options I am looking at are Codeberg and self-hosting a Forgejo instance. Which brings me to:
3.) How heavy is Forgejo to host? I've got doubts that it will fit on holenet's current VPS, and I'm not sure I can eat the cost of a larger/second instance. My ISP would rather that I not have a web server on a residential account and I'm not sure what the extra cost per month will be. And there's no colo places near me to rent space from (and if I did I think it has to be a rack mount server and not me cobbling together something from the i7 9800X-flavored parts from my previous rig)
4.) How painless (or painful!) is it to contribute or interact with a git server/forge that *isn't* on the same platform? Like, if someone was still using GitHub or GitLab or Codeberg and my repo was self-hosted, would they be able to do forks and make PRs without needing to make accounts on my server?
Okay so, it looks like self-hosting a project with an open development model that welcomes outside contributions is Not A Very Smart Idea (because that means you have to be a GitHub and I am NOT moderating that!), so it looks like I will be migrating the Sonic Worlds Next repo to Codeberg. But, I won't be migrating until I get some actual, concrete solutions for the Discussions feature; apparently there is a feature request for this for Forgejo, which powers Codeberg, but "SLIPPERY SLOPE!" https://codeberg.org/forgejo/forgejo/issues/410
@techokami@woof.tech If someone wants to contribute, then they need to have an account on the service the repo is hosted on.
For example if it's on a self hosted forgejo instance, then they need to register an account on it.
If the repo is public, then everyone can clone it without an account and upload it on any other service (basically "forking")
@techokami@woof.tech it's pretty light to host, I have a personal instance on a $2.50 OVH VPS, but that is only 20 GB of space that gets filled up pretty quickly if openai is spamming requests to the point of crashing logrotate
@lyze@woof.tech well then, looks like it'll be Codeberg over self-hosting, but I still need to find out about migrating discussions...
@techokami@woof.tech Seems like there's no in-built export tool for githubs discussions feature, therefore you'd need to write your own script to export them via its API: https://github.com/orgs/community/discussions/3315#discussioncomment-11638497
@cthuflu@social.cthuflu.com so what are the requirements in terms of software deps? I'm asking because I once tried to run something that people claimed was light on a light VPS, and the entire thing was crushed by Node.js (a dependency) being rather heavy and eating all the resources
@techokami@woof.tech Regarding 2: Here are the discord webhook settings:
Techokami
