manned_meatball

joined 1 year ago
[–] manned_meatball@lemmy.ml 2 points 1 year ago* (last edited 1 year ago)

My own intricate system of 4 git repos to manage dotfiles, bash initialization, cli tools/scripts, and system state.

The last one keeps track of installed packages and "dotfiles" out of the home directory (system config files like /etc/hosts).

[–] manned_meatball@lemmy.ml 4 points 1 year ago

as one of their customers, I second this

[–] manned_meatball@lemmy.ml 8 points 1 year ago* (last edited 1 year ago)

Is there a web archive equivalent to github repos? At least for the most popular ones.

I know there are hard copies in Svalbard's seed vault, but they're more for a one-in-thousands-of-years post-apocalyptic scenarios than this.

[–] manned_meatball@lemmy.ml 1 points 1 year ago

if you need less than 4TB just get a solid state

[–] manned_meatball@lemmy.ml 5 points 1 year ago (1 children)

I got the HL-L2325DW last year. Connecting it to the WiFi using WPS was really easy. Making the desktop see it was a bit of trial and error, but it was partially thanks to the PDF viewer I was using, so I'd recommend printing from a well established viewer like Okular or the web browser, at least for the first use.

I don't remember having to download any drivers manually from their website btw, I just chose it from the list when setting up a new printer. This process might change with the distro and desktop environment though, I'm using Kubuntu.

In fact, if you're a bit lucky, the printer might even show up as a "discovered device" after you connect it to your network, even with a suggested driver and connection so you just need to press next.

[–] manned_meatball@lemmy.ml 13 points 1 year ago

"Desktop OS" also counts laptops. Unless people are working from their smartphones, I don't think desktop is collapsing at all.

[–] manned_meatball@lemmy.ml 17 points 1 year ago

thankfully it's usually the other way around: the glass is opaque and only transparent with power. So you don't need to worry about an ill-timed power outage.

[–] manned_meatball@lemmy.ml 8 points 1 year ago (1 children)

And even if open source doesn't fit their business model for any reason, there should be regulations that force these companies to open source everything in any situation that they stop offering support.

[–] manned_meatball@lemmy.ml 1 points 1 year ago
function command_one() {
    # activate the environment
    source "$XDG_DATA_HOME/venvs/alpha.sh"
    # run the thing
    actual_command_one
}

function command_two() {
    # activate the environment
    source "$XDG_DATA_HOME/venvs/alpha.sh"
    source "$XDG_DATA_HOME/venvs/bravo.sh"
    # run the other thing
    actual_command_two
}
[–] manned_meatball@lemmy.ml 2 points 1 year ago (2 children)

possibly never going to happen

 

I've been using Portainer to manage my homelab stacks from a single dashboard, which is more convenient than the CLI, but I'm not very satisfied with it so I've been looking for alternatives.

Portainer often fails to deploy them and is either silent about it, or doesn't give me much information to work with. The main convenience is that (when it works) it automatically pulls the updated docker compose files from my repo and deploys it without any action on my part.

Docker Swarm and Kubernetes seem to be the next ones in line. I have some experience with K8s so I know it can be complex, but I hope it's a complexity most paid upfront when setting everything up rather than being complicated to maintain.

Do you have any experience with either one of these, or perhaps another way to orchestrate these services?

[–] manned_meatball@lemmy.ml 0 points 1 year ago* (last edited 1 year ago) (2 children)

lol I literally did this yesterday for my job, using dashboard 1860 too. I used a docker compose stack following their guide here.

[–] manned_meatball@lemmy.ml 3 points 1 year ago (1 children)

The devs are calling it alpha themselves.

view more: next ›