Did you waive your rights to the code anywhere? If not then it's still your code and they used it without obtaining the rights to using it - depending on your jurisdiction ofc.
Hi, nice project. Why would I use your project over similar (open-source) projects like sharry and lufi?
I personally would prefer to use those alternatives because their source is available and can be reviewed, I didn't see any reference to your source code - which is fine, but a no-go for me personally.
Hmm. The first section about cloud service providers is a bit weird to me. There are providers which "keep my best interests in mind" as part of their business model, backblaze would be one. Their whole idea is to provide a good backup services. Encrypting my data before transit also doesn't make me worried that it will be accessed by them or any of their employees because they will only get some garbled mess.
Compare that to google, another cloud service provider. Their business model is to make money by selling me ads (foremost), they do that by gathering as much data as possible. Here all my answers would be negative.
This puts me in an awkward spot where I nearly every time answer with "Neither agree nor disagree", because there is more to it and not because I don't have an opinion.
Do you still have the live iso you used to install arch? Does it work? Do other distros work (just the live systems are enough)?
Edit:
Some more things: Did you try disconnecting the pc from mains, pressing the power button (to discharge all capacitors) and reconnecting. Reseat the button cell for the bios?
Docker container can't read a bind mount. Permission issue? No, it's SELinux, again. And I didn't even install it explicitly, it just got pulled in by another package.
And to be clear, the issue isn't SELinux really, but unexpected non standard behaviour which I never asked for (never explicitly installed it).
You are talking about funkwhale. I never tried it, so I can't speak to the part about integrating it with different clients, but that surely is possible, if it doesn't already work.
Also, one big problem with this is copyright (however you might feel about it).
Looks good, I use a lot of the stuff you plan to host.
Don't forget about enabling infrastructure. Nearly everything needs a database, so get that figured out early on. An LDAP server is also helpful, even though you can just use the file backend of Authelia. Decide if you want to enable access from outside and choose a suitable reverse proxy with a solution for certificates, if you did not already do that.
Hosting Grafana on the same host as all other services will give you no benefit if the host goes offline. If you plan to monitor that too.
I'd get the LDAP server, the database and the reverse proxy running first. Afterwards configure Authelia and and try to implement authentication for the first project. Gitea/Forgejo is a good first one, you can setup OIDC or Remote-User authentication with it. If you've got this down, the other projects are a breeze to set up.
Google: Laughs in "Everybody else you communicate with who has that shit enabled"