Egregoros

Signal feed

API Docs
Timeline

Post

Remote status

Context

9
bajax

bajax

@bajax@baj.ax remote
Open link
[CW]

Content warning

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

Show
@phnt I fucking HAAATE docker for this very reason. it has made lazy dev practices too convenient... they can always tell their users "oh download our docker image!" without much of any, IF any, provision for running the software standalone.

have to deal with this shit at work and it's annoying as fuck
shibao

shibao

@shibao@shitposter.world remote
Open link
[CW]

Content warning

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

Show
@bajax @phnt then don't, just treat the `Dockerfile` as an instruction list with no bullshit, just commands. i prefer that over super long winded installation scripts that need to explain all the steps instead of just giving me commands to run
bajax

bajax

@bajax@baj.ax remote
Open link
[CW]

Content warning

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

Show
@shibao @phnt I'm not gonna be able to explain to you why that's unacceptable lol. it amounts to "hassle" but I suspect you're gonna have what amounts to a moral objection to that so I'll just leave it there. (is there a way to have a patch you can set on dockerfiles so you can use automatic updates and automatically apply your changes? then you only have to get into it if you touched something that changed)

I've started using ansible to set up shit, maybe I can have an LLM routine that converts dockerfiles into roles or something.
shibao

shibao

@shibao@shitposter.world remote
Open link
[CW]

Content warning

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

Show
@bajax @phnt the whole point of docker is that it create a repeatable setup in an environment like an ansible playbook, except every time the docker image is built you're actually executing the ansible playbook and you're guaranteed to get the same thing because you're starting from a fresh instance of ubuntu or alpine or whatever the base image is from the beginning. the "hassle" is the load on maintainers that people who can't linux and expect the maintainers to do their weird custom linux admin for them

>suspect you're gonna have what amounts to a moral objection
what? this is all practical, not moral. you're the one moralizing about how a repeatable setup is bad and you won't explain why to me because you view it as "bloat" or something and want the maintainers to handhold you on making guides so that you can use your weird custom linux setup rather than using what the maintainer has decided to support for their software
shibao

shibao

@shibao@shitposter.world remote
Open link
[CW]

Content warning

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

Show
@bajax @phnt i don't get why you're shitting on this thing that you don't understand fully

>is there a way to have a patch you can set on dockerfiles so you can use automatic updates and automatically apply your changes?
yes you create a custom dockerfile that just like how the normal dockerfile starts from the ubuntu image and adds commands and whatnot for it, you just have a custom dockerfile that starts with whatever software's dockerfile you're using and then add commands on top of it, which basically amounts to you following a software's installation guide and then deciding to do more commands after you're done with it. but with docker, it's repeatable and idempotent (or supposed to be in theory at least)
Replying to @shibao@shitposter.world
Phantasm

Phantasm

@phnt@fluffytail.org remote
Open link
[CW]

Content warning

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

Show
@shibao @bajax
>you just have a custom dockerfile that starts with whatever software's dockerfile you're using and then add commands on top of it

And now do that for every Docker software you want to use that ships a Postgres install in Docker compose, just because you might want pg_repack in there.

Replies

0

Fetching replies…