08:38 <npulido> sb0: can you confirm if the mailing lists are up? I would then repost...

09:04 <lkcl> there's mailing lists? excellent!

09:54 <mtrbot-ml> [mattermost] <sb10q> @npulido the problem should be fixed but since it has to do with DNS it'll take some time for caches to update

09:56 <mtrbot-ml> [mattermost] <sb10q> so, discourse is about as bloated as gitlab and is also a CPU/memory hog even when doing nothing; and additionally they want you to install the docker crap

09:57 <mtrbot-ml> [mattermost] <sb10q> they also have those scripts for n00bs that tell you stupid things like you *must* run them as root when you don't (being in the docker group is sufficient) and refuse to run

09:58 <mtrbot-ml> [mattermost] <sb10q> that's easily fixed of course but that doesn't give me a good impression of the general sanity of the decisions in this project

10:07 <mtrbot-ml> [mattermost] <npulido> Alright, so I understand that what I sent to the list last Friday will eventually get posted (when caches update), or should I send the email again?

10:08 <mtrbot-ml> [mattermost] <sb10q> it might get posted, I'm not sure. did you get a bounce notification?

10:09 <mtrbot-ml> [mattermost] <npulido> no, I got nothing

10:10 <mtrbot-ml> [mattermost] <npulido> I guess it went in then?

10:10 <mtrbot-ml> [mattermost] <sb10q> no. your email server may be still retrying, and may post it at some point.

10:12 <mtrbot-ml> [mattermost] <npulido> alright, then I'll wait and if nothing happens I will repost. Thanks for looking into it.

12:32 <whitequark> sadly that's how web applications seem to be deployed these days.

12:32 <whitequark> I mean... when I was doing webdev, that was standard, except instead of docker you'd have something saner like chef or puppet. (Relatively speaking saner.)

12:33 <whitequark> but if you try to do this with people who want to run this on random linux distros your workload just skyrockets, and you spend all your time explaining to people how to configure postgres on their slackware fork or whatever

12:34 <whitequark> not really sure what can be done about it, it's a general admission of defeat with the way distros work

12:35 <whitequark> maybe distributing as nix recipes would be a better alternative to distributing docker images, not that it'd take any less memory

12:38 <daveshah> , z09azd2ay8z,

12:40 <cr1901_modern> That password is now compromised daveshah :)

12:43 <whitequark> that seems more like a cat tbh

12:45 <daveshah> Yes

12:45 <daveshah> was cat

12:45 <cr1901_modern> Plz post cat pics

12:47 <cr1901_modern> whitequark: Is puppet/ansible/etc solely for setting up your system configuration just after you (re)installed the os image? Or can you use it to bring in new software (such as a web application) after you've used your OS for a while?

12:48 <whitequark> cr1901_modern: you can use ansible to manage your laptop

12:48 <whitequark> even

12:49 <whitequark> it's just a more structured way to run apt-get or put files in /etc

12:49 <whitequark> unfortunately it's still extremely ad-hoc and breaks all the time

12:52 <cr1901_modern> Can it also be used to download and compile source (for the stuff not in repos)?

12:55 <whitequark> sure, you can run arbitrary shell commands if you want

13:29 <cr1901_modern> Playbooks look like a superior method to my "hints" directory, where I put the command line invocations to build complex pieces of software (like llvm and rust)

13:52 <whitequark> yep

13:52 <whitequark> I like ansible quite a bit

13:52 <whitequark> but it's trash compared to something like nixos

14:07 <cr1901_modern> Aesthetically, I don't want a hyperstatic environment for every application on my system, although I think it's a cool idea.