Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)S

SayCyberOnceMore

@ Cyber @feddit.uk

Posts
12
Comments
485
Joined
3 yr. ago

  • Ok, not heard of Moode. The website looks interesting, I'll check it out, thanks!

  • Ah, interesting, so you can use mopidy with HA? Interesting... not thought of that connection.

    I have the Volumio integration with HA, but I've not looked at it recently.

    Thanks

  • I remember trying piCorePlayer when I was considering alternatives to Volumio3 and - from memory - the UI was a bit weird?

    Like, it started in one UI, but then you had to do a few things to get to another?

    But, ok, I'll take another look as I'd forgotten about it. Thanks

  • Yeah, this is what I'd like clarified too

    Am I just setting up a schedule on the server and then pushing out config to the other devices and can then shut down the server? (For example)

    Where do I need to install restic?

    Is this local only or to an offsite (Hetzner) location?

  • Let me know which repo this update appears in.

  • I had a quick look at the docs... so, can I backup my DB version X and restore it to DB version Y?

  • It's difficult to do security-only updates when the fix is contained within a package update.

    Even Microsoft's security updates are a mix with secuirity updates containing feature changes and vice versa.

    I usually do an update on 1 random device / VM and if that was ok (inc. watching for any .pacnew files) and then kick Ansible into action for the rest.

  • 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.

  • Not really.

    Depending on how you install things, the package maintainers usually deal with this, so your next apt update / pacman -Syuv or ... whatever Fedora does... would capture it.

    If you've installed this as a container... dunno.. whatever the container update process is (I don't use them)

  • 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.

  • Or

    ?

  • Not heard of foam...

    I'm not a programmer (as a day job), so I don't use vscode, which makes me think I'd be learning to use the "wrong" tool for the job (for me), but I'll take a look, thanks.

  • Thanks, yeah, this is kinda what's happened with Logseq.

  • Ok, not even heard of that one, I'll take a look. Thanks

  • 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

  • I think you have enough people here stating their pfSense / OPNSense works fine, so I'd guess you have something unique with your setup - maybe it's a dodgy cable, or you're running both In & Out traffic over vlans on the same NIC on your PC and getting problems with unmanaged switches dealing with that...

    I had an issue with my pfSense box not negotiating to 1Gb on a Cat6 cable to a switch. I tried all sorts of diagnostics and it turned out to be a problem with the wall socket crimping, so hardware issues do need to be checked... I'm obviously assuming you didn't use the exact same cables as your firewalla...

    Just some different angles to think about...

  • Lowest common denominator: Plaintext / Markdown files?

    They'll work with Logseq, web browsers, notepad, your phone... and maybe sync it all via syncthing?

    That's what I use.

    I also write up my system notes in Logseq with the intention that I'll just sync in my ansible files too... one day...