• Quik@infosec.pub
    link
    fedilink
    arrow-up
    53
    ·
    10 hours ago

    One thing the author probably hasn’t done yet or doesn’t mention is that you can configure .container services with systemd (often called quadlets), e.g. a simole MariaDB this:

    [Unit]
    Description=MariaDB container
    
    [Container]
    Image=docker.io/mariadb:latest
    Environment=MYSQL_ROOT_PASSWORD=rootpassword
    Environment=MYSQL_USER=testuser
    Environment=MYSQL_PASSWORD=testpassword
    Environment=MYSQL_DATABASE=testdb
    
    [Install]
    WantedBy=multi-user.target
    

    Short intro Full reference

    This is superb, because it means your containers finally feel well-integrated with the rest of the OS and you can use systemctl, journalctl, etc. just like you would with other services.

    • Fedegenerate@lemmynsfw.com
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      1
      ·
      9 hours ago

      Excuse me, peasant crontab enjoyer here, but what?! I could write a (mostly) declarative system without having to learn Nix?! I should probably be learning systemd anyway, it’s looking more and more like the present, let alone the future.

      I run a bunch of remote reverse proxies that are functionally identical, but for having a different Cloudflare key and calling for a different static IP

      Could I write the entire config to a self hosted Git > pull that repo > change those two variables and have a running machine?

      Remote updates have been kicking my ass, I either can’t wrap my head around Screen or it isn’t fit for my need. Being able to pull the new config from Git over Tailscale and then run it would be game changing for me.