(Justin)

Tech nerd from Sweden

  • 0 Posts
  • 193 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle










  • C developers are basically the angry neighbor complaining that the city is building a bike lane.

    Biking is really popular these days, because it’s healthier, cheaper, and better for the environment than driving, but new residents moving to the neighborhood will only move in if there’s good bike lanes. Now, nobody is asking the C developer to give up their car, but they’re still mad about the bike lane. They can’t be bothered to learn how to drive alongside bicyclists, and they say that bicyclists just have to deal with the fact that the C developers might run them over, and they should just get a car. All the bicyclists are afraid to use the bike lane because people keep getting run over by the C developer, and the C developer refuses to learn new driving techniques to share the road with bicyclists.

    This eventually leaves to all the bicyclists moving to another city where they can bike safely, and the C developer’s neighborhood turning into a shithole ghost town with no developers left, all because the C developer is an asshole who can’t accommodate change.








  • Generally it’s simpler if you have your NAS separate from your application server. Synology runs NAS really well, but a separate application server for docker/etc is a lot easier to use and easier to upgrade than running on Synology. Your application server can even have a GPU for media transcoding or AI processing. Trying to do everything on one box makes things more complicated and fragile.

    I would recommend something like Debian or NixOS for the application server, and you should be able to manage it over SSH. You can then mount your NAS as an NFS share, and then run all your applications in Docker or NixOS, using the NAS to store all your state.