@bender@twtxt.net What would make standing up Yarn even easier? I can think of a few things that people might struggle with: a Domain, Pointing the domain at something valid, Maybe a reverse proxy setup. Running yarnd itself is just downloading a binary and configuring it (which could also be easier)

@prologic@twtxt.net I remember when I first ran Yarn on arrakis, it was a mess. Remember I had to start it again from scratch? If I were to run Yarn today, I will have to ask you what -u to use, if I am going to run a web server on it (say, Caddy), and what to do to keep the huge cache Xuu and I like. LOL. Granted, I could figure it out myself after some trial and error too.

To make Yarn install easier? An installer script that would prompt for the settings, generate config, and install the systemd, because, whether we like it or not, the biggest Linux distros around use it.

@bender@twtxt.net I avoid install scripts like the plague. This isn’t Windows and they’re usually poorly written. I think it’s better to prioritize native packages (or at least AUR, MPR, etc) and container images.

@prologic@twtxt.net I remember running yarnd for testing on a couple of different occasions and both times I found all the required command line options to be annoying. If I remember correctly, running it with missing options would only tell you the first one that was missing and you’d have to keep running it and adding that option before it would work.

This was a couple of years ago, so I don’t know if anything’s changed since then. It’s really not a big problem, because it would be run with some kind of preset command line (systemd service, container entrypoint) in a production environment.