Little bit of everything!

Avid Swiftie (come join us at !taylorswift@poptalk.scrubbles.tech )

Gaming (Mass Effect, Witcher, and too much Satisfactory)

Sci-fi

I live for 90s TV sitcoms

  • 16 Posts
  • 393 Comments
Joined 2 years ago
cake
Cake day: June 2nd, 2023

help-circle
  • It’s out of date, and in desperate need of a rewrite. PHP might have been an okay choice 15 years ago, but no one in their right mind should be using PHP for modern server development. (Yes I’m calling out Pixelfed too). With so many languages and frameworks, that’s probably one of the worst right now.

    Then it was proven that they don’t really get modern infrastructure either, as their docker containers depend on stateful code, with combinations of environment variables and php files that need to be stored in volumes, and then plugins which are also stateful - meaning that on new updates they need to go through an “update” process. This is directly opposite of good practice as docker containers should be 100% immutable and be able to run just by using docker run. They also have required volume mounts scattered throughout the OS, it was just never designed with containers in mind.

    I can’t recommend nextcloud right now, it’s incredibly brittle and slow.


  • Agree with others, if you try to do a replica it’s going to be very inefficient, and your costs will be high. You’re looking for a backup, then just nightly/weekly you perform your backups. Any blob storage then will do, just work out what pricing works for you. Just plan out how you’d do a restore in case everything came crashing down - from ground up how would you bring your services back online?


  • HDD enclosure is a fine way to start, as long as you know it has limitations. Eventually you’ll probably need more storage, and it won’t scale. That being said, you can get 26TB hard drives now, it’ll be a while. Just make sure you plan out how to back it up. Remember the rule - if you can’t afford to buy a backup then you can’t afford to do the project. Make sure you have backups in mind.

    If you decide to upgrade to a full NAS solution later also remember that during that migration you probably will need to use new hard drives while migrating as your current ones will need to be copied from to the new NAS, meaning you will probably end up with a few redundant drives. Not a huge thing, but there will be no “in-place” upgrade. It all depends on where you want your homelab to go in the future.


  • Yeah Proxmox leaves a lot to be desired in terms of metrics. However, metrics are supported out of the box. Bad news, you probably won’t get what you want within proxmox. Good news, you have another project you get to undertake! Hooray!

    Like I said, Proxmox supports metrics out of the box. If you go Cluster -> Metric Server you’ll be able to see that you can add a metric server. The first iteration I did with proxmox I added an InfluxDB container which then proxmox can talk to (yes they can be on the same host), and then proxmox will start pumping metrics into InfluxDB. (It uses Telegraf under the hood). Then, you can also run Grafana, add your InfluxDB as a data source, and then you have a sweet metrics dashboard. There are a lot of pre-built dashboards already made that look great, and you can customize from there.

    You can also use Graphite, I personally haven’t used it, but I also dropped Influx over time too. These things evolve in that sort of way. That’s how I’d get set up and started though.



  • Did a takehome for a company recently that did it well. They required that I make a docker file (you could give them one if you wanted) where when ran it would run tests. It was a neat use of docker IMO, it standardized that builds were just “build the docker file” and running was just “run the dockerfile”. You would t have to deal with tar or anything then.

    Thousand ways to skin a cat there



  • They said they were open to it but they had zero priority of doing it themselves, and essentially “submit a PR if you want it”. A shame really, their interface is great, and such an easy setup. If they implemented either xmpp or matrix I would switch immediately. All of my friends want a discord clone that “just” works, but no one wants to go to this server for this group and then login to that server for that group. They want a single-pane interface like what discord offers.

    Shortsighted to not implement that IMO.





  • Replicating images isn’t really best practice. Images are meant to be ephemeral on the server. Dockers pattern is to repull the images if they are needed, and that only takes a few seconds. Saving the images IMO would just be a waste of space.

    If you are afraid the images will be gone someday, the proper way to handle this is to use a docker registry as a proxy. So you make your own docker registry, like your.tld/registry and then set it in proxy mode. Then when you pull your images you set docker to pull from your registry. If it’s found it will use your local data otherwise it will pull through from the parent registry, and serve the docker image to your client. For backup then you backup the registry’s volume.

    That fits within the pattern of docker. Your clients come up, query the local registry, and it will serve your containers. Your server remains ephemeral.