• 0 Posts
  • 14 Comments
Joined 1 month ago
cake
Cake day: January 2nd, 2025

help-circle

  • Onomatopoeia@lemmy.cafetoSelfhosted@lemmy.worldNAS Hardware selection
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    14 hours ago

    Consider how the NAS will be used. Is it just file storage, or will you want to stream from it?

    If just file storage, you can use lighter hardware.

    I’m running a 5 year old Dell Small Form Factor desktop as my NAS/media server. It’s power draw is under 12 watts unless I’m converting files. There’s room for 3 data drives (boot drive is M2). It has no problem streaming, unlike my consumer NAS. And it cost way less.


  • This may not fully solve the problem, but have you tried using it through Hermit or Native Alpha? These are browsers designed to make websites work like apps on Android.

    Combined with my password manager (Bitwarden), it’s usually as fast or even faster than some apps, with a side benefit of a single app install rather than an app for each service.

    So far this has worked well for Amazon, Walmart, libraries, my healthcare login, bank, ebay, Home Depot and Lowes, etc.





  • So, paid app (if you want wireless sync) - Media Monkey.

    The Android app can read network shares and network media servers (I forget exactly what it can read). But it works best if you run the server app - then you can stream the library or sync media, similar to iTunes.

    The Android app is free for basic functionality ($5 for wireless sync), the desktop/server app is free ($30 to enable wireless sync and a few other features). It’s been worth it for me. Even the free versions work very well.



  • Documentation has been mentioned already, what I’d add to that is planning.

    Start with a list of high-level objectives, as in “Need a way to save notes, ideas, documents, between multiple systems, including mobile devices”.

    Then break that down to high-level requirements such as “Implement Joplin, and a sync solution”.

    Those high-level requirements then spawn system requirements, such as Joplin needs X disk space, user accounts, etc.

    Each of those branches out to technical requirements, which are single-line, single-task descriptions (you can skip this, it’s a nice-to-have):

    “Create folder Joplin on server A”

    “Set folder permissions XYZ on Joplin folder”

    Think of it all as a tree, starting from your objectives. If you document it like this first, you won’t go doing something as you build that you won’t remember why you’re doing it, or make decisions on the fly that conflict with other objectives.