Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 07/01/2024 in Article Comments

  1. well the best solution is a separate server with its own domain or sub-domain, with its own certs. however you can it is doable. solution 1: the easiest solution would be to change the port babble uses. by default if you are on https, it uses port 443, otherwise port 80. problem on a server running a web server, those 2 ports are already in use and nodejs wouldn't be able to use them. so you would need to open up a port in your servers firewall, a port that isn't used by something else. this has its own set of problems tho, the first one is having to open up another port on your servers firewall. the other problem it opens up, networks often block all ports except 80 and 443, so people on those networks wouldn't be able to connect to babble. like i mentioned, this is most def the easiest solution, its not really the most ideal one. solution 2: in nginx and apache there is such a thing called "reverse proxy" (well in one of them its called that, in the other it has a different name, but i can't remember which or what it is, but its the same thing more or less). basically with the reverse proxy, you setup your webserver to handle the connection to nodejs internally. this one requires a bit of work to setup, on apache it requires a few modules to be installed. in my testing back in the day, i found nginx to be the easiest to setup (as its built in functionality) and it also performed a fair bit better imho than apache does. to me this is the ideal of the two solutions i give here. it doesn't require any ports to be opened, it also looks cleaner. solution ?3 there might be other solutions, it's been since like 2016/17 since i last looked into alternatives. the service really rendered those solutions kinda moot, as everyone on the self hosted version jumped ship for the service. was gonna have the live events be a "customized" room, that would be open to everyone (or restricted if you wanted it). then at the end of it, you'd issue a command to close it down, and the room would disappear and its content would be added to pages (if it is installed, or give you an option to have it just archive itself and/or to pages). it would be fun to try to add a chat bot to it. it has 'bots' but nothing too complex, but get one of these natural language models like chatgtp or tabbyml (which is free, and customizable, but would require its own setup too, but i haven't played with tabby's chat ability). babble is very customizable. you can set it up where you can have private rooms, private messages, rooms have a ton of configuration to them, there are "bots" (even the ability to add in your own custom bots), command (ability to add in custom commands), there are also different layouts for it, which i might remove. the "global bar" was never popular, even tho i thought it was cool as hell . it will make building it easier if i took out the global bar. anyway, if you have anything more specifi in mind, don't shy away, let me know.
    1 point
  2. custom projects or releasable apps for the masses? i'm open to either one, for custom work, will need to check my schedule
    1 point
×
×
  • Create New...