CapillaryUpgrade @ CapillaryUpgrade @lemmy.sdf.org

Posts

2

Comments

50

Joined

2 yr. ago

Don't put yourself down! Using systemd wouldn't make it work "better", it's just more "proper" (and a great tool to know in general!)

Great job and keep going!

This is really cool!

Where did you put the service file?

I don't mean this as critique, but as possible next project, since your solution works perfectly fine. Systemd has some cool features that could make this project have a bit fewer moving parts:

• a .mount file could replace the mount and unmount script, and handle logging too! (I am pretty sure you would need separate files per mount, though, so "fewer moving parts" might be a bit of a lie, depending on your interpretation)
• that "After=" setting you used, can also be used to check for network connectivity. IIRC it's "networking.target" on Fedora, at least. You might want to double check the systemd docs if After is the right one for this, as I have a hard remembering the systemd dependency intricacies.

That way you would end up with a .mount file per mounted directory, with logging using journald, and no external scripts.

I really like systemd as it can be a great tool, when you start to break down the complexity of it.

I hope you get well soon and get the best you can from this time.

Cockpit is great.

It's pretty simplistic. It gives you an overview of your system ressources and handles libvirt VMs and Docker (i think. I used it with Podman, but in this context both should work).

My impression was that the container and VM interfaces were pretty simple, and I wouldn't have liked it as my main interface for those services, but it would be perfect for getting an overview and restarting them!

Grounded danish plugs don't fit Schuko sockets, but Schuko plugs fit danish sockets (but aren't grounded).

This leads to a staggering amount of ungrounded devices in Denmark, as most are imported and making a variant for such a tiny country isn't profitable.

Fun fact: the danish power plug was created by Lauritz Knudsen, a Danish company who had a monopoly. They are the reason Denmark uses this plug as the only country in the world, and Schuko only became legal to install in houses quite recently, so 99% of houses still use their standard.

LK has since been bought out by Schneider Electric but we are still stuck with our special plug and most imported devices are still ungrounded.

Thanks for listening to my Ted Talk.

Node-Red can do dashboards. I don't know if it does data logging, but I would guess so since it can do dashboards. It also supports MQTT so it should handle ESPHome devices without a problem.

It's made for automations (and great at it) but it can be a minimalist HA hub too.

Hook it up with ChatGPT and you are golden!

I run the built-in automatic rpm-ostree upgrade service every 6 hours.

If you think that's too inefficient, maybe read the docs for shutdown.target and see if you can use that to run an upgrade service before shutdown?

I'm not too experienced with that part of systemd but it seems like it could be a "proper" way to run things on shutdown?

Use a passphrase (not a password) and a physical security key, like a yubikey. It also supports TOTP or whatever 2fa Proton uses, you just connect it with a laptop or phone and it gives you a key.

A physical key is much more secure than 2fa from a password manager (although both are probably fine)

Nextcloud doesn't verify your email and has tons of other nice features as well. ProtonDrive (/ProtonMail as another user suggested) probably doesn't or you could use your Proton address for that.

You mention allowing weak passwords are a plus. Please use a weak password, especially without email as 2nd factor.

Have you considered using mnemonics for your passphrase?

Generate a number (i would use around 5) of random words (EFF has a wordlist, humans are really bad at randomness) and link them together using silly images. For example:

• sparrow
• window
• automobile

First, you link sparrow to window: imagine a sparrow trying to break through a window, not just flying into it by accident, no, this sparrow is mad and is set to destroy it.

Second, you link window to automobile: imagine an automobile with huge windows. The car is completely normal sized except every window is at least 3 meters tall. It looks absolutely ridiculous and you feel embrassed that youvhave to drive it everywhere.

Repeat this proces for the rest of the words. It helps remembering them if the image makes you feel something, like making you chuckle or feel angry that you have to deal with this stupid contraption (only in your mind, hopefully)

Also, make sure each "link" is distinct. Eg. Don't make the second link an automobile driving into a window when the sparrow does the same. It will mess up the order and make you jump around between similar mental images.

I only tried running rootless when i set them up several years ago and i was completely green, so it was probably me who was the problem.

Regarding podman-compose, Fedora repos has a a package that aliases podman -> docker and the regular docker-compose package, which i used before migrating to podman+systemd. It worked flawlessly unless i did networking shenanigans because Podman and Docker differs (/differed?) in so some thing simply couldn't be brought over.

Edit: i found the docker-compose and Podman alias thingies in a Fedora Magazine post.

However, unless you use docker-compose a lot for other stuff, learning to use Podmans systemd integration (also called quadlet) is very much worth it. They're just a really powerful combo and systemd has a ton of nice features for making stuff run and keep running.

Podman is CLI and API compatible with Docker (except where differences in implementation doesn't allow it)

Running Podman as root is 99.9% the same as running Docker.

I have been running my homelab with Podman for several years and it is absolutely mature enough for a regular user.

Also, the docs are really good.

Oh, i did not know. Thanks!

No problem! I'm glad you got it working!

I would just pull the first filament away from the bed and the rest usually follows along and you get a little birds nest.

I barely use a calculator, but you could try SageMath if you like the thought of writing you math in Python.

I mean inserting the pause gcode command in the slicer. The idea is that this command is very basic, so every printer supports it, as opposed to a filament change command.

I used Cura and IIRC you could add "move away from the print and move back when unpaused" commands.

I haven't 3d printed for far too long, so my memory is very blurry. You might be better off looking for a Youtube video or googling for a tutorial, but it wasn't rocket science once someone on the internet explained it to me.

Edit: maybe try searching for something like "3d printer filament change pause"

You can also just pause it and change filament manually.

Just remember to push through some of the filament until the color comming out is right.

Then use Bugzilla. That will show you are ready to flail yourself for the good of the company /s

Sorry, but i find that platform so painful to use.

On a more serious note, i think some of the "github-style" (Gitlab/Gitea/Forgejo) can migrate between each other.

Check out if that's true and if so, try them all!

Forgejo/Gitea are probably the most common "low-resource" (read: doesn't use a couple of GB RAM, like Gitlab supposedly does) code forges.

Do you want to impress future employers by running an enterprise-grade bugtracker or by showing that you can document your work with meaningful bug reports/etc.?

If it's the first option, consider Gitlab, if it's the second option, what ever you like.

There already good recommendations, so i'll just add that you shouldn't make your work life harder for the sake of running Linux.

Definetly give it a go, and see if it fulfills your needs, but maybe hold off on nuking your Windows install until you are satisfied.

I use my Linux computer for personal stuff and some work stuff (web-browsing, email, office suite) and i have a separate Windows PC just for running applications specific to my field, which don't have Linux versions or alternatives (or where it makes the most sense for me to use the industry standard)

Because they will quickly use up a ton of storage just for showing other instances content, or did i misunderstand you?

That is a good question, but methods like pruning old content from other instances might evolve into a path for solving this (very real problem).

Federation as it stands right now is a terrible system.

I beg to differ. Right now federation is an okay solution. My proof is that it at least works, and that the problem you mention isn't killing the fediverse (yet).

We should not forget that ActivityPub is a W3C standard, (which itself is a huge milestone for a decentralized internet) and like other similiar standards (eg. HTTP) it can be iterated on and improved when solutions to new or old problems are found.