Egregoros

Signal feed

Timeline

Post

Remote status

Context

19
[CW]

Content warning

re: Self-hosting is dead, long live self-hosting

Show
@phnt imo the "docker slop" complaints are actually bullshit. if i have host installs, then i end up having to debug everyone's custom package manager configs and system stuff, and I already kind of do, i get issues with things like weird custom docker replacements and systems like that. All of my apps are just completely standard elixir apps that can be installed with the standard phoenix install instructions, and if anyone wants to do host installs and knows phoenix, they would easily be able to run the like 3-4 commands to get the app installed. but i don't publish those instructions because people then will want to try and install those and then i end up having to do debugging for people in the form of bug reports of "shit no worky". I already sometimes have to do that with reverse proxy instructions/networking. If big projects want to have host install instructions, I think they can be good and such, but everyone complaining about lack of non-docker install instructions when literally just opening `Dockerfile` will literally give line by line instructions of commands to run off base ubuntu or programming language or whatever images, I find is incredibly telling. People complaining about docker slop but will refuse to look under the hood of the software they run are exactly the kind of people I (and I assume) and other software maintainers are trying to filter out with docker-only instructions
[CW]

Content warning

re: Self-hosting is dead, long live self-hosting

Show
@shibao @phnt if your docker has to install tons of shit to work is it really appropriate for docker? honest question. usualyl I feel like I just want it to isolate a binary and maybe a few libs we know won't be shipped
[CW]

Content warning

re: Self-hosting is dead, long live self-hosting

Show
@sun @phnt there are definitely shitty docker installs that need a bajillion sidecar scripts and stuff, for sure. don't run those software because they're shit. quality devs will make very optimized, clear and simple docker images that aren't huge with unnecessary layers and bullshit. the number of docker-compose.yml files I've seen that are absolute dogshit are immediate clear signs that some of these devs need to stop writing software.
[CW]

Content warning

re: Self-hosting is dead, long live self-hosting

Show
@sun @phnt i mean revolt being horribly buggy microservices for absolutely no fucking reason before they gave up on allowing it to be self hosted is not a docker problem. but people treat it like docker is the problem
[CW]

Content warning

re: Self-hosting is dead, long live self-hosting

Show
@sun @ageha @phnt docker is the closet thing we have to a universal distribution packaging solution that we have but then people rage against docker because it goes against whatever they consider idiomatic for their distro and not realize that they're the problem why every single non-rolling-release distro is hell on earth when you have a bug or vuln that's fixed by the latest version of whatever you're using
[CW]

Content warning

re: Self-hosting is dead, long live self-hosting

Show
@shibao @sun @ageha At this point it is mostly clear to me you didn't even read what I originally wrote, and mostly skipped what I wrote in this thread, or you don't understand what I wrote. You seemingly saw the term "Docker-slop" and instantly lost your mind. As a result, this thread has turned into the equivalent of both "The crypto question" Codeberg issues where its just goes around all the time.

I'll copy the cores of my take below:
But another side-effect of this is that the user has learned nothing in the process, and at least to me self-hosting also is about learning about the setup (or at least was when I entered this hobby).

I'm even gonna go as far as making the argument that using these "easy install" options is also detrimental to the project maintainers, because they now have to figure out what is broken from user's that have no idea how anything in the system works.
If a user goes through a well documented manual install option, they learn about the setup in the process.

---

If you are a developer of a self-hosted application and Docker is the only supported way of installing it, stop. A docker install option is not bad itself, especially in the current climate of shipping universal binaries on Linux being almost impossible, but it being the only option is not a good idea. Your software should not be that hard to install/compile that Docker is the only sane option for users.
I probably won't bother replying to this sub-thread anymore. There is no reason to do so anymore. You keep thinking I'm some sort of a Docker-hater despite me literally acknowledging its benefits and it being a useful tool for building universal "packages" in the Linux space while it being nearly impossible to do so without it.

I'll reply to this though:
>if i used phnts suggestion i would be using outdated versions of libvips and i presume other libraries. and this is alpine, not even something like ubuntu or whatever. this is why i use arch

I've been an Arch user for 5 or 6 years and now a Gentoo user for a year. Your point is completely irrelevant in the context of what I wrote above as well. This is not about library versions at all, its about giving users reasonable choices of installation that are easy-enough to support and not writing convoluted software that needs to run in a container. That is the whole point of what I wrote, nothing more, nothing less.
[CW]

Content warning

re: Self-hosting is dead, long live self-hosting

Show
@phnt @sun @ageha >At this point it is mostly clear to me you didn't even read what I originally wrote, and mostly skipped what I wrote in this thread, or you don't understand what I wrote. You seemingly saw the term "Docker-slop" and instantly lost your mind.
yes i did ignore all your ad hominems as they are not constructive discussion. but I will respond now so that you can know that I don't appreciate them, and you should stop using them going forward.

please learn about docker and don't just think you know about docker when implying that shipping software with a tool that sets namespaces, cgroups, files in a certain layered file system and handles networking makes people unable to understand how these regular processes on their devices that they control are running. nothing is being hidden and obfuscated, it is a personal choice for someone to decide not to inspect how things are running if they're using a certain technology, just like it is a personal choice for someone to not think about the commands they are being asked to run in an installation guide. The tools are not to blame for your abstraction purity spiral which can apply to anything, even the commands you are asking me to provide you to run
[CW]

Content warning

re: Self-hosting is dead, long live self-hosting

Show
@shibao @sun @ageha
>yes i did ignore all your ad hominems as they are not constructive discussion. but I will respond now so that you can know that I don't appreciate them, and you should stop using them going forward.

Please point them out then, because I'm not aware of any I made except maybe this:
>I also find it incredibly telling that you don't bother pasting said install instructions into a markdown file and write a guide around that.

Which is a reply to your:
>>but everyone complaining about lack of non-docker install instructions when literally just opening `Dockerfile` will literally give line by line instructions of commands to run off base ubuntu or programming language or whatever images, I find is incredibly telling

If you still think this whole thing is about your software, it simply isn't. I've already told you and I'm telling you again. I didn't even know you shipped Cannery in a Docker container prior to this whole conversation.

This still stands:
>I probably won't bother replying to this sub-thread anymore. There is no reason to do so anymore.
[CW]

Content warning

re: Self-hosting is dead, long live self-hosting

Show
@phnt @sun @ageha >You seemingly saw the term "Docker-slop" and instantly lost your mind.
telling people they "lost their mind" is considered derogatory

>If you still think this whole thing is about your software, it simply isn't. I've already told you and I'm telling you again. I didn't even know you shipped Cannery in a Docker container prior to this whole conversation.
i wasn't and it still isn't, that's why i didn't bother to talk about it, i'm still just talking about docker in general

>I probably won't bother replying to this sub-thread anymore. There is no reason to do so anymore.
yeah i'm trying not to bait you and i agree, i think i've said what i've wanted to say and need to get all my chores done today
[CW]

Content warning

re: Self-hosting is dead, long live self-hosting

Show
@shibao @sun @ageha
>telling people they "lost their mind" is considered derogatory

I apologize for that, I'm sorry. From the tone of what you wrote yesterday and today, you seem(ed) to be angry, which is what I was pointing at.

Replies

11
[CW]

Content warning

re: Self-hosting is dead, long live self-hosting

Show
@shibao @phnt @sun @ageha software EQ drives me mad. I went through the trouble of buying a measurement head to EQ my headphones, but then none of it matters because easy effects can't auto switch based on what you plug in so you end up using profiles for different hardware
[CW]

Content warning

re: Self-hosting is dead, long live self-hosting

Show
@rees @phnt @sun @ageha >can't auto switch based on what you plug in
i mean i do this for like directly connecting to noise cancelling headphones, or wired audio out, or through my dac, but for the different headphones with my dac i have to switch manually cuz there's no way for it know what headphone i have plugged into my dac which is understandable