The backend seems to be a fairly standard Rust project, you basically run `cargo build --release` and then deploy the binary. For the frontend, it seems like a pretty standard frontend project, you install dependencies, then run build command and you have a bunch of website assets you deploy to your server.

Overall, seems pretty standard and easy to deploy. Most complicated would be to also run the various services that are supporting the backend, but again, not overly complicated.

Is there something specific that is missing to be able to self-host this?

I think it's pointless to selfhost if you have to recompile an app in order to connect to your server. The team should have a field box to add a server URL.

It doesn't look like this is the case? I'm looking at https://github.com/revoltchat/self-hosted/blob/master/README... where you are told to update 2 config files.

I couldn't even find them. Do you have a link?

I'm sorry, but what??

The self-hosting guide even walks you through setting up the VPS on a specific platform. What more do you want? One could even argue that if you need your hand held through setting up a VPS, you probably shouldn't be self-hosting anything, so from that viewpoint, these instructions are a lot more friendly than they had to be.

> ...if you need your hand held through setting up a VPS, you probably shouldn't be self-hosting anything...

Since when does IT tell corporate what to do?

You and I both know that corporate calls the shots, and if they tell someone to do this, and that's not their field of expertise, they'll need their hand held.

There are plenty of non-profits and other orgs that have IT staff of 1, and that guy is IT because he knows how to format a word doc.

Your argument is a bit disingenuous.