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/)CU
Posts
4
Comments
1,032
Joined
1 yr. ago

  • Yes you can. You select what it is at import.

    I'd also suggest not setting up your torrent client (or not enabling it) u til you've finished your import, and setting what you are monitoring and what you are not.

    This way you can just import, and enable/disable monitoring of items easily before you start any new downloads.

  • Its well worth it IMO, makes service segregation so much easier. It may help to toss a router off your main network, and start experimenting that way, give you a decent place to mess things up - which is, again purely my opinion, one of the best ways to learn.

  • Ah - yeah ive got trunk to each of the machines in my clusters, 9 vlans total, and of course I can add more whenever this way. I'm a bit of a glutton for naming and numbering structure too, so the purpose of the service determines which VLAN its on. Like Home Assistant has just about its own vlan, with sensors and misc tools in support of it all there. A different one for IoT devices by others (that I will never trust with internet access, so its initiate from another VLAN on the FW only, outbound can't be initiated from any device on it, etc), one for work thats part of a site-to-site with work, with a few ports on the switch allocated that I can just plug in ad hoc, etc.

    Definitely helps to have the range to play it this way!

  • In my case, I don't need the isolation of a VM, really I'm just looking to separate the service I'm running into something manageable and easy to move between hosts. I could do a VM for each, but I'd be adding overhead and power requirements without much benefit.

    And really that'd all it comes down to for me. Each service is its own LXC, from stuff most self-hosters use, to random one-offs I write. Managing it all stays in ansible for everything, and the structure is quite a bit simpler.

    When I do want to bring it elsewhere, I van package it up clean and toss that on a new LXC somewhere else quickly, like an 80 core monster with $16k in GPU thats already getting pushed hard, and knowing it will be of almost no impact to its main job while adding the service it needs.

    I do still have VMs, but that is to do things like dealing with windows. Especially specific versions, like a piece of software for some work stuff that requires XP or server 2008 specifically. Its pretty isolated though, not even allowed network access out. All my writes are to a thumb drive if I need to get something out of it (which is uniquely set as the thumb drive its allowed to see).

    So nothing that I couldn't do a bunch of other ways, this is just the structure thats working best for me.

  • Tiny/mini/micro.

    You can grab a used box for under $200. Most I've picked up have been around $100-$125, then I drop in a new m.2 for the host, maybe add/change ram depending on what I got it with.

    Data lives on the NAS (really multiple for me, but besides the point here), and you'll get waaaayyyyy more compute with a usff PC like that than you will with a pi or what a NAS can offer. They also run really light on power when you aren't putting the CPU to work, so budget friendly in a bunch of ways.

    I've got a goal after a move my wife and I are planning to run the whole shebang on solar, with battery and a switch to utility power. I've got 10 of these little monsters now, after a recent addition, and its quite doable from my measurements of actual power usage.

    Which is a really long way of saying you may want to look at some tiny/mini/micro PCs.

  • I'm more of an LXC kind of guy, but I get the switch. I don't do much docker these days, outside of a few work scenarios outside of my control.

    Personally I don't like RH under IBM, so I won't go with fedora either. Fantastic community, bad business behind it (a story as old as time).

    Its one of the reasons I appreciate Debian as much as I do, and contribute with Sid as often as I can, mostly using sid as a mirror of what I'm doing on my Deb stable boxes and finding breaks.

  • The worst part about "simple" is defining what that means for the person. Depending on what they mean, there are a lot of different answers.

    (And a good chunk of those are just Debian with different branding).

    As others have said, EndeavourOS is pretty damn easy too. Personally I'll stick to Arch for desktop, deb stable for servers/lxc's, and deb sid for mostly screwing around and sending some reports in so stable can be stable.

  • That happens for me for any link that can't be handled in Voyager, but I think when it comes to images the thumbnail doesnt load either....

    Out of curiosity, is it maybe your instance and how its caching? Have you tried other instances? Let me grab a random post that works for me as an example.

    https://lemmy.dbzer0.com/post/37713149 works for me for reference. Tap and right to fill screen.

    Edit: BTW, tapping these images will also go full screen. Not sure if you have that issue with embedded so figured I'd mention.

  • None in particular, but there is enough known to be able to put it in question relative to the alternatives.

    I will say that quite a bit of the case reminds me of current day parents who kill their kids, intentionally or not. Whether they thought it would blow over since kidnapping for ransom was more common then, or attention, whatever, I have no idea.

    Given the only physical evidence tying to the crime had no fingerprints on it, or anything else to tie to the crime itself, combined with the last...

    I can only think "if thats what happened".