Formerly /u/neoKushan on reddit

  • 0 Posts
  • 513 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle




  • Kushan@lemmy.worldtoSelfhosted@lemmy.worldDocker is hard work
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    2
    ·
    14 days ago

    You’ve done the hard work building the compose file. Push that file to a private GitHub repository, set up renovate bot and it’ll create PR’s to update those containers on whatever cadence and rules you want (such as auto updating bug fixes from certain registries).

    Then you just need to set up SSH access to your VM running the containers and a simple GitHub action to push the updated compose file and run docker compose up. That’s what I do and it means updates are just a case of merging in a PR when it suits me.

    Also I would suggest ditching the VM and just running the docker commands directly on the TrueNAS host - far less overheads, one less OS to maintain and makes shares resources (like a GPU) easier to manage.

    You should look at restic or Kopia for backups, they are super efficient and encrypted. All my docker data is backed up hourly and thanks to the way out handles snapshots, I have backups going back literally years that don’t actually take up much space.




  • And batteries. Arguably batteries would have the biggest impact out of all of those; turn every household into a virtual power plant and the grid can self balance, especially during peak usage.

    The government is also dragging its feet on V2G which would allow your EV to act as an additional giant battery that can feed the grid and your home when usage is high, then top it back up overnight.

    There’s been a big storm in the UK, so wind is generating fuckloads of energy right now, to the point where energy providers are having to pay people to use electric - all that cheap power could be filling up batteries instead.










  • It was a couple of weeks ago for me but I managed to get my docker compose script for all my infrastructure cleaned up and all versions of containers are now pinned.

    I have renovate set up to open PR’s when a new version is available so I can handle updates by just accepting the PR and it’s automatically deployed to my server.

    Nice and easy to keep apps up to date without them randomly breaking because I didn’t know if a breaking change when blindly pulling from latest.




  • I generally agree with the sentiment but don’t pull by latest, or at the very least don’t expect every new version to work without issue.

    Most projects are very well behaved as you say but they still need to upgrade major versions now and again that contains breaking charges.

    I spebt an afternoon putting my compose files into git, setting up a simple CI pipeline and use renovate to automatically create PR’s when things update. Now all my services are pinned to specific versions and when there’s an update, I get a PR to make the change along with a nice change log telling me what’s actually changed.

    It’s a little more effort but things don’t suddenly break any more. Highly recommend this approach.