@silvereagle@david That's nuts. How do their own users feel about it? tech.lgbt is a 4K user instance. Cutting off that many people over not liking some mods is absurd, unless there's serious abuse coming from the instance.
@nando161 this is a really good point. It isn't about being guilty for something your ancestors did, its about looking around you and like — hey, there's this deeply unjust system, don't you want to dismantle that? Wouldn't you even if your ancestors weren't responsible, because justice matters to you?
@archlentil it is in fact very cool!! it gives you a web-based dashboard to manage all of the docker containers necessary to actually run a full nextcloud instance, where you can enable and disable services with a checklist, and click to see the logs of each server in your browser, and use a graphical user interface to stop and restart and see the status of each container, and it'll even notify you when there are updates for your Docker containers as well! The only hitch is that if you try to set Collabora up according to what their docs say, it won't work. Instead follow this guide:
@archlentil@rose this I what I'm using: https://github.com/nextcloud/all-in-one . It seems like it was the most logical choice because it's all of the relevant doctor containers assembled into a single system that you can manage through a web dashboard and stuff and it's got everything implemented even the stuff people commonly forgot to set up like redis
@rose thank you! but idk if that'd help much. I'm trying to use next Cloud all in one which is a Docker container that sets up and runs like seven other Docker containers to get the whole thing including collabora setup it's just poorly documented and confusing
@rose okay yeah using the other docker container's fake IP address works inside an exec bash at least, let us see if the web interface likes it (I bet it won't)
@rose what's going on is that I wanted two docker containers exposed on different ports on the server to talk to each other via just the server's web address and the relevant port, because the address is modifiable in one of the docker's web UIs. I can access the docker that's supposed to be contacted myself, but the actual docker that needs to talk to it can't.
@rose oh god.... why can't the machine just talk to itself? AAAAAAA this is why I'm a software developer not a sysadmin this shit just hates you and wants you to die lmao
I'll try doing sketchy shit with the docker IDs and see what happens I guess
Hey does anyone know how to make it so that a server can curl or ping its own domain or public IP (without just editing that domain into the hosts file, since I Need a Doctor containers to be able to talk to the server as well so just editing the domain into the hosts file as localhost won't work on the containers bc for them localhost means themselves)? Been really stumped on this one
@jadedtwin thats how i am too! I can watch shit about big ass fighting robots or whatever and as long as it's internally consistent and the rules have benefits and drawbacks and stuff I'm totally fine
@weilawei gotcha. As I said, due to the already kind of established medical capabilities of my setting there is actually something that can be done for the ribs so there's that going for him at least
"Keep your flag black and your head up, kid."Egoist mutualist anarchist.Punk lesbian trans woman.Hacker. Solo netrunner. CS major.Interested in anarchist, existentialist & poststructuralist philosophy (Nietzsche, Stirner, Proudhon, Carson, Foucault), epistemology, and daoism. Also hard SF, cosmic horror, and epic fantasy. I write all these things as well.I love punk music like Against Me!, Bad Religion, Anti-Flag, and Pat the Bunny.Chronic Post-Concussion Syndrome sufferer.