tuhriel

joined 2 years ago
[–] tuhriel 2 points 1 week ago

Yes, and the media is printing and retelling that shit, without questioning it....

[–] tuhriel 1 points 2 weeks ago

That actually makes sense...thank you!

[–] tuhriel 2 points 2 weeks ago

But, but think about the children....of the executives, do youbreally want that they have to work? You monster!

/s

[–] tuhriel 5 points 2 weeks ago (3 children)

My biggest gripe with yaml (especially in docker-compose files) is that l, for me at least, it is absolutely not clear when I need to add dahes (-) in front of multiple entries and when it's just linebreaks.
And there are no easy accessible docker-compose validators...

[–] tuhriel 2 points 1 month ago

On the one running on my parents side I run raspberryOS. I do have an rpi on my side which is triggering the script and vpn (and also backs up their NAS) That one is running NixOS, but raspberryOS works fine.

[–] tuhriel 2 points 1 month ago

Also it seems to be a good energy storage...for cases where you have irregular energy production. Create hydrogen via electrolysis using the energy surplus from wind, photovoltaic etc.
And if you need the power, you get it back via fuel cells.

I think I saw a documentary about the shetland islands, where they have (or had) a power surplus from wind farms mich grater than they where able to transfer to the main land.

I guess these are the cases which make sense...but creating another supply network to bring the hydrogen fuel everywhere might not be the way to go...

[–] tuhriel 8 points 1 month ago

Yeah, you are probably right...if your reviewer is so lazy, it can be "bribed" with "don't write anything bad about me", it gets what it deserves.

What I'm more concerned is all those LLM-zombies which are listening to these reviews without knowing they are sloppy LLM-reviews. Should they check their sources? Hell yes! Will anyone do it? Unfortunately, no...

[–] tuhriel 19 points 1 month ago (2 children)

I'm a bit torn on this one...it's a big f-you for all those low effort "reviews", which I like.

On the other hand, it still is cheating....

[–] tuhriel 2 points 1 month ago* (last edited 1 month ago) (2 children)

I have a remote backup setup at my parents, which consists of a rpi4 and an external hdd (old NAS HDD). The rpi also has a wireguard interface running. If I need to back stuff up (via a restic-rest container) I open the vpn from my side, start the container, mount/decrypt the hdd and trigger the restic update. Afterwards everything gets disconnected again.

The rpi needs to be always on and you need to be able to forward a port to the rpi.

The data should be secure though, as the disk is encrypted and not mounted. (You can even store the decryption key on your side of the network, so you need the vpn to be able to mount the hdd)

[–] tuhriel 3 points 2 months ago

Thanks for the link. It seems they got it somehow working on DSM6, but if I check the thread, it's a lot of ducttape and locktight involved especially to run with DSM7. Might try it out on a rainy sunday

[–] tuhriel 1 points 2 months ago (2 children)

Give me a package that runs on my ds214play and I'll switch in a heartbeat

[–] tuhriel 2 points 2 months ago

So...in the future it is "this e-mail could have been a meeting"

 

Hi everyone I'm currently in the process to move one of my RPI4s from RaspberryOS to NixOS and I'm struggling to setup one of the services.

On the RPI I have a python script that is creating offsite backups via a Wireguard tunnel:

  • Open the wg tunnel
  • mount and encrypt the external disk on the offsite RPI
  • mount the source from my nas
  • start the restic-rest server container offsite
  • trigger the restic command to backup to the restic repo

allthough it's a bit overkill it works quite well for a few years now. Since most of the tasks are actually outsourced to systemd units those where quite easy to setup in nixOS. What I'm struggling is, how can I create a virtual python env to run the python script. All the guides I found for managing python dependencies are usually for development and use nix shell

My current workaround is, that I copy the script and requirements.txt from my script repo and create the venv manually. This does work, but I feel there is a better way, maybe the whole setup is already on the wrong pat as I tried to solve each hurdle separately?

Here's my current implementation of the remotebackup module (the wireguard and mount units are in different modules):

{inputs, config, pkgs, lib, ... }:

let configpath = builtins.toString inputs.infra-configs;
in
{
systemd.tmpfiles.settings = {
  "remotebackup" = {
    "/var/lib/remotebackup" = {

      d = {
        group = "root";
        user = "root";
        mode = "755";
      };
    };
    "/var/lib/remotebackup/assets" = {

      d = {
        group = "root";
        user = "root";
        mode = "755";
        };
      };

    };
  };

sops.secrets = {
  "restic/remotebackup/rest" = {};
  "restic/remotebackup/restic" = {};
};

sops.templates."remotebackup" = {
  content = ''
  {
    "rest" : "${config.sops.placeholder."restic/remotebackup/rest"}",
    "restic": "${config.sops.placeholder."restic/remotebackup/restic"}",
  }
  '';
  path = "/var/lib/remotebackup/assets/restic.cred";
  };


system.activationScripts.addPythonScript = lib.stringAfter ["var"] ''
    cp ${configpath}/scripts/remotebackup/script/restic_remotebackup.py /var/lib/remotebackup/restic_remotebackup.py
    cp ${configpath}/scripts/remotebackup/script/requirements.txt /var/lib/remotebackup/requirements.txt
    chmod 733 /var/lib/remotebackup/restic_remotebackup.py
    cp ${configpath}/scripts/remotebackup/script/assets/backup_paths.txt /var/lib/remotebackup/assets/backup_paths.txt
    '';

}

Also, on the RPI I'm triggering the script with cron, according to the wiki cron should be replaced by systemd.timers. Would you also suggest moving to systemd.timers

P.S.: If at all possible, I'd like to keep the script within my script repo...

view more: next ›