SayCyberOnceMore

  • 17 Posts
  • 745 Comments
Joined 3 years ago
cake
Cake day: June 17th, 2023

help-circle






  • I split my loads (gigity) between the power hungry NAS and a passively cooled low power Proxmox host.

    For me, most 24/7 activities are low CPU - like Home Assistant, so it needs to be there, but it doesn’t need to do anything.

    Other VMs are ansible, uptime kuma, smokeping, etc… the most they use is RAM

    Then the (relatively) more power hungry NAS powers up 3 times a day to syncthing everything, maybe upload a backup, and if no-one’s using Immich, etc. then it’ll power back off again.

    The only other thing I have yet to downsize is my pfSense box (still a low powered device, but has fans…) and a Raspberry Pi I use for my Zigbee network.


  • My NAS powers up & down about 3 times a day. Drives are all fine & healthy and some have been in there for years.

    I don’t disagree with your core point though…

    If the drive just finished spinning down and then it’s triggered for a 1 byte file, spins down, repeat… yeah, that definitely needs sorting out.

    Just the initial spin-up lag would do my head in.

    But off & on ~ daily, yeah not a problem.





  • Layers

    HA has it’s own built in IP ban function with the HTTP(S) Integration, but that might only see NAT’d addresses (ie the entire internet has the same address as far as HA is concerned), and is really only intended for protection from someone already on your network.

    You should also have some other form of external facing brute-force protection with HAproxy, nginx, fail2ban, etc.

    You should have a firewall somewhere, maybe a function on your router, maybe a separate box. If possible also use geographical IP ranges to only allow your region(s).

    All of that can either be at home, or on a VPS if you wanted to bounce all your traffic via a fixed location, perhaps with an outbound VPN from your home to the VPS.

    Also use other network presence detection (ie ICMP ping, GPS, etc) to determine if you’re at home.

    Or… as others mention… support the devs with their solution.


  • I setup a standard Arch install, added BTRFS, NFS, SMB, restic (for offsite backups), etc and haven’t looked back.

    I installed Cockpit thinking we’d need a GUI, but syncthing just works to mirror our laptops & phones with the NAS, and with multiple versions (by syncthing) I’m happy so far

    The only thing that I had issues with was Immich and (major) postgresql updates, but that’s stablising now. And, TBH, the worst thing was just having to scrap the DB and just let it rebuild it (for a few days…)

    I went with BTRFS because I can “see” it with standard linux tools like gparted, clonezilla, etc. So I can backup and modify the NAS OS itself, not just my data.

    Apart from updates, I haven’t touched it for years.






  • Yeah, personally, I think they’d gradually make it db first and then markdown will gradually become an import / export function.

    And I don’t need colab… my notes are mine. Yeah, there’s a few I share (ie home stuff with my partner), but for work, personal stuff, nope… just me.

    But yeah, after ~3 years of almost daily note taking for work, it needs a computer with SSD to find things quickly and can take a while to start on the phone (hence using Markor to edit the .md files directly instead)

    To your original post, yeah, single maintainer… but Logseq has how many? And it’s stalled really… from an external viewpoint.

    I think SilverBullet has a slow steady pace rather than Logseq’s fast initial pace and then … nothing much since they got lots of investment - which someone will want back.


  • Thanks for the insight.

    I need a UI that I can navigate links between files / topics / dates, so whilst I agree about the editor point (I use Markor for quick notes / edits on my phone), I need to be able to look up points during live meetings.

    And to your last points, yes, I’m trying to understand it, but it’s on-ramp is an almost vertical wall for a complete starter like myself… but maybe I’m hitting it too fast