• 1 Post
  • 1.33K Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle
















  • atzanteol@sh.itjust.workstoSelfhosted@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    1 month ago

    squeezing every last drop of resource form tired old hardware

    This is such a myth. 99% of the time your hardware is doing there doing nothing. Even when running “bloated” services.

    Nextcloud, for example, uses practically zero cpu and a few tens on mb when sitting around yet people avoid it for “bloat”.




  • I’m not sure how the *arr stuff works but hard links don’t let you “edit a file while preserving the original” - they let you have mulltiple paths to the same file.

    $ echo "hello" > file1
    $ ln file1 file2
    $ echo "world" > file2
    $ cat file1 file2
    world
    world
    

    Does *arr have some sort of copy-on-write behavior? Some modern file-systems have de-duping behavior and copy-on-write built in that you may be able to save some space with.

    But the point of topic 1 was to simplify. You can keep doing your hardlink stuff but standardize it and simplify setup/configuration. If you always do things in the same way it’s less complicated to keep track of and fix.

    You’ve understood the difference in terraform/ansible, and yeah terraform is probably not going to be as helpful. Ansible would be much more likely to help. It can seem burdensome to have to write configuration files for things at first, but it forces you to do things in a way that is standardized and repeatable.