thirdBreakfast @ thirdBreakfast @lemmy.world

Posts

19

Comments

194

Joined

2 yr. ago

If you didn't have to deal with a cumbersome spacesuit, I imagine you could run, but you'd lean over much more towards the horizontal - like maybe 45° or lower, so each 'step' would be a push backwards in line with your longitudinal axis. Don't waste energy by bounding up.

Source: wild speculation.

Yo dawg, I put most of my services in a Docker container inside their own LXC container. It used to bug me that this seems like a less than optimal use of resources, but I love the management - all the VM and containers on one pane of glass, super simple snapshots, dead easy to move a service between machines, and simple to instrument the LXC for monitoring.

I see other people doing, and I'm interested in, an even more generic system (maybe Cockpit or something) but I've been really happy with this. If OP's dream is managing all the containers and VM's together, I'd back having a look at Proxmox.

If we're making a list of great projects written in Go, I'm putting in a word for PocketBase which is a based around sqlite that works as a backend-as-a-service and does all the tedious auth work for you. It's the perfect sideproject backend.

This is where I landed on this decision. I run a Synology which just does NAS on spinning rust and I don't mess with it. Since you know rsync this will all be a painless setup apart from the upfront cost. I'd trust any 2 bay synology less than 10 years old (I think the last two digits in the model number is the year), then if your budget is tight, grab a couple 2nd hand disks from different batches (or three if you budget stretches to it,).

I also endorse u/originalucifer's comment about a real machine. Thin clients like the HP minis or lenovos are a great step up.

Absolutely Tailscale - I use it for this exact situation of Syncthing from my NAS. Simple to set up, and secure.

This. Hosting at home might be cheaper if you are serving a lot of data, but in that case, the speed's going to kill you.

I'm a keen self-hoster, but my public facing websites are on a $4 VPS (Binary Lane - which I recommend since you're in Aus). In addition to less hassle, you get faster speeds and (probably) better uptime.

This is insightful. Also some of the niche communities that came over have probably found it hard to recreate the experience with less participants - whereas when they were historically established on Reddit only when was enough traffic to justify splitting off from a more general topic.

Perhaps over time the members of smaller niche Lemmy communities will drift into more general topics. For example if there's not enough participants to maintain a vibrant 'wearing feathers in your hair' community, those members would probably be welcome, and valuable participants, in the larger 'head ornaments' community. Since I'm slightly invested in the success of Lemmy, I certainly hope that's what happens rather than people going back to '/r/featherhairwearing'.

Thanks - I thought it would be something like this I just hadn't made the effort. Calibre-web just runs as a server?

Bare metal servers, VPSs, or VM's you host? If it's for VM's you host, then consider Proxmox as hypervisor and use VM templates. I'm sure old school sysops could to the same with QEMU and Virtmanager or something. But basically, I just set up a VM exactly how I like it, then convert it to a template and cookie cutter it out.

I can sense the Nix guys shaking their heads - it's on my list to try :- )

I've just been down this exact journey, and ended up settling on Kavita. It has all the browse, search and library stuff you'd expect. You can download or read things in the web interface. I'm only using it for epub and PDF books, but its focus is comics and manga so I expect it to shine there.

I don't think it does mobi, but since I use Calibre on my laptop to neaten up covers and metadata before I drop books on to the server it's a simple matter to convert the odd mobi I end up with. Installation (using docker inside an LXC) was simple.

It's been a really straightforward, good experience. Highly recommend. I like it better than AudioBookshelf (which I'm already hosting for audio books) which I also tried, but didn't like as much for inexplicable reasons. I also considered Calibre-Web, but that seemed a bit messy since I guess I'd use Calibre on my laptop to manage my books on a NAS share then serve it headless from the server with Calibre-Web? I might have that completely wrong, I didn't spend any time looking into it because Kavita was the second thing I tried and it did exactly what I wanted.

It has a practical element (Hello Jellyfin, Kavita, AudioBookshelf & Syncthing), but for the rest of it, it's about 60% hobby and 20% learning stuff that could be potentially career enhancing.

Gnu/Linux absolutely annihilating server operating systems means that I can run the same stack, and use the same tools, that giant companies are based on. All for free. In my spare room. 1L x86 computers cost less than two packs of cigarettes! Little SSD's are ridiculously cheap. And you don't even need that stuff - that old laptop in your cupboard will do. Even if you kick in to donate for your software (and I recommend you do if you can) it's a cheap hobby compared to golf or skating or whatever. Anything you need to learn there's blog posts and videos available.

We live in an amazing time in this hobby. I know there's companies that would like to take it away from us, but Open Source just keeps kicking goals. Thank you FOSS developers, Gnu, Linus, FSM, Cthulhu and the other forces in the universe that make this possible.

There's a project called Filebrowser that allows you to edit text files in a web interface. You can just run that on the 192.168.1.2 machine. It's easy to set up simple auth, and you can restrict it to the /data/ directory.

Built my own quad-copter and flew it around. Had to flash plane ESC's with custom firmware, wire it all up manually to a controller and muck around with the values to tune it, then you could hand fly it (very carefully). It was amazing! - an RC plane that could hover.

Nowadays, if I go somewhere and some normie's "flying" a DJ, I'm annoyed with them. It's really breathtaking how good these got so quickly.

I don't sew, but a follow several people who do (for vintage and modern clothing) on Instagram - just to emotionally vampire off their irrepressible happiness when it all comes together and they make something that comes out as great as they imagined (lots of "and it has pockets!!!" moments) or they master a new skill they had been struggling with - like sewing button holes in denim or whatever.

It's not for me, but I love the obvious satisfaction and joy other people are getting out of it.

+1 for Tailscale. It's a vital piece of the system for me now.

Your head might be spinning from all the different advice you're getting - don't worry, there are a lot of options and lots of folk are jumping in with genuinely good (and well meaning) advice. I guess I'll add my two cents, but try and explain the 'why' of my thinking.

I'm assuming from your questions you know your way around a computer, can figure things out, but haven't done much self-hosting. If I'm wrong about that, go ahead and skip this suggestion.

• Jellyfin good - a common gateway drug to homelabbing, and the only thing you'll do that non-tech friends will appreciate
• Proxmox good - it makes the backups simple and provides a path forward for all sorts of things
• Docker good - you've said it increases complexity; this is correct in that you're adding more layers of stuff, but it reduces your complexity of management by removing a heap of dependency issues. There is a compute and memory overhead involved, but it's small and the tradeoff is worth it.
• VM good - yes an LXC is more efficient, but it's harder to run docker in. Save that for a future project
• Media data somewhere else good - I run a separate NAS with an SMB share. A NAS in a VM is a compromise, but like all things self hosting, you start out with what you've got. I let Jellyfin keep the metadata in the VM that's hosting my Jellyfin though since the NAS is over the network. That's less of a consideration if you are visualizing your NAS on the same machine, but I'd still do it my way for future proofing.
• Passthrough magic not yet - this can also be a future project. If your metal has quicksync that can be utilized to reduce the CPU load, but that can also be a future project.

Same, but with the jellyfin/jellyfin image. Been solid for me, less dramas than raw on the OS. Two cores and 8GB for the VM (in Proxmox), media on a NAS, metadata on local SSD.

I have a very similar setup. Jellyfin in Docker on a Debian VM (2 cores, 8GB RAM), and all the media on the NAS. The CIFS/SMB from the NAS is mounted in fstab. I keep all the metadata locally for speed - ie not on the NAS. I don't like the extra layer of running Docker, but it works like a charm whereas I had a few hassles running Jellyfin natively in the VM. I do have a special 'media' user with the name and password in the mount command which only has permissions for the media.

Can't comment on the arrs suite since I get all my linux distros on those disks attached to the front of magazines.

Thanks for going back and updating with your solution - I'm gonna check that out.