• 1 Post
  • 19 Comments
Joined 1 year ago
cake
Cake day: January 13th, 2024

help-circle







  • Nighed@feddit.ukOPtoSelfhosted@lemmy.worldNew to self-hosting
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 months ago

    What do you want to run in a VM that can’t run in Docker?

    a VM with torrent client and a killswitched VPN was the easiest way to get a secure setup. also meant if it ever got virused I could just roll it back. I need to look more into what docker can actually do by the looks of it.

    You are the second person to suggest unraid - is it ok to sit on the perpetual license (for a few years at a time), or are the updates really required? It supports GPU passthrough right, so I can have a ‘normal’ linux desktop for gaming while running the other stuff in the background?

    TY for the response!




  • Nighed@feddit.ukOPtoSelfhosted@lemmy.worldNew to self-hosting
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    2 months ago

    ah sorry, my new ISP gave me a router, but it doesn’t have any VPN functionality on it (Edited OP to make that clear). My old one probably can’t support the speed, and for some reason doesn’t let me change its MAC address, so I can’t use it as the ISP facing device.







  • You want them all in one place so that they can be uploaded in one go to your fitness tracking site. That lets you see what your HR, power and cadence all where on that specific hill for example.

    I used to have a Fitbit that used my phone for GPS and it was awful and drained the batteries on both devices. I guess the idea of having 5G is that you don’t actually take your phone with you, one less thing to have to force into your pockets.



  • I’m almost always of the opinion that refactoring is better than a rewrite as long as the tech stack is supportable.

    Everyone wants to rewrite stuff, because the old system is ‘needlessly complicated’. 90% of the time though, they end up finding it was complicated for a reason and it all ends up going back in. It does allow a system to be written with the full knowledge of its scope though, instead of an old system that has been repeatedly bodjed and expanded. Finally, if your old tech stack is unsupportable (not just uncool, unsupportable) then it can be the most feasible way. It will take ages though with no/little return until it’s all finished.

    Refactoring is more difficult, as developers need to understand the existing codebase more to be able to safely upgrade it in situ. It does mean you can get continuous improvement through the process though as you update things bit by bit. You do need to test that each change doesn’t have unexpected impact though, and this can be difficult to do in badly written systems.

    Most Devs hate working on other people’s code though, so prefer rewrites.

    (Ran out of time to go into more detail)