Skip Navigation

Posts
19
Comments
194
Joined
2 yr. ago

  • I'm on iOS. I've been testing a beta of Jello that looks really promising, but as a beta has a bit of distance to go. I'll check out Feishin though - thanks for the recommendation.

    I'd love Jellyfin to turn out to be the solution, but I suspect it's not, at least yet.

  • I've got three of these little 1L HP's, one for production, a spare, and one for development. But really, it's a small load - that list would happily run on an old nuc. The constraint is really memory which I've mostly addressed by moving from VMs to LXCs. And I could be even more efficient by just running all the docker containers on one host if I had to.

    Storage for media and backups is a Synology NAS.

  • how to access the NAS and HA separately from the outside knowing that my access provider does not offer a static IP and that access to each VM must be differentiated from Proxmox.

    Tailscale, it will take about 5 minutes to set up and cost nothing.

  • Infrastructure:
    • Proxmox VE - everything's virtualised on Debian, mostly in docker inside LXC's for neat backup/restore and moving between nodes
    • NGINX Proxy Manager - in front of most of my homelab services so they have https certificates
    • Tailscale - access everything, everywhere, including on phone, securely
    • Uptime Kuma - monitoring, with ntfy notifications
    • apt cacher NG - unnecessary caching of apt updates
    Apps:
    Currently in testing on the dev server:
    • neko - virtualised browser. Been experimenting with this in a container with a VPN for really simple secure browsing - ie launch it, do your online banking and then destroy the container.
    • Dashy - I go through periods of wanting a pretty home page with all my services, set it all up, then fail to actually use it and eventually delete it, then hear about another cool one...
    • Sharry - securish file sharing. I don't love just emailing my accounts off to the accountant.
    • LimeSurvey - survey software (like Survey Monkey) - just something I'm testing for work
    • Omada controller - I've got a TP-Link switch and WAP that don't really need centrally controlled, but you know, can be.
    • A couple of development environment LXCs I use VS Code in

    I still have not landed on a music system. I've put some of my library on Jellyfin, and tried a couple of apps with, but haven't hit on a good combination yet. [edit:formatting}

  • Yes, in a shallow tourist mine in Australia. Apparently coal starts to flake easily once it's been exposed to air for a bit, so they kept a big chunk in a large jar of water that you could take out and handle. It felt like a light wet rock.

    The sample, and the coal at the workface of the mine was stereotypicaly black. We wore hats with lights on, and when we emerged back out to the daylight I had an overwhelming urge to speak in a Monty Python type Yorkshire accent and go home and have my back scrubbed clean of the coal dust by my swarthy tired looking wife while I sat in a tub in front of the fire in the kitchen and our urchins played in the street.

    I don't want to give the impression I'm a big fossil fuel tourist, but I've also seen blobs of crude oil on beaches near Mediterranean sea oil terminals.

    Sadly, I didn't try to set fire to them on either of these occasions, which I now regret.

  • I hand grind for the Aeropress with a Timemore C2, which I gather would be good enough to get me started with espresso.

  • This, or two turnbuckles joined at the top point with a couple of links of chain.

  • Your last point about concentration could also explain @Uninformed_Tyler's thoughts about the AeroPress being somewhat forgiving. Most of the extraction takes place when the water is clean, then the rate of extraction drops off quickly and then idles along for a bit - so the cut off time is not so critical.

  • lol - you are probably right, I'm over-thinking it. The coffee I drink every day now (with an acceptably small amount of fiddling around) is reliably excellent. Perhaps I don't need to watch the Aeropress movie ;-)

  • I read somewhere that GoPros and other action cameras are one of the least used purchases, so I figured "that should mean there's plenty on eBay". So grabbed up second hand bargain, played around with it for a couple of weeks, bought some extra batteries and other accessories, and since then it's sat in the cupboard except for a single occasion.

    Turns out you don't need an action cam if you're not getting any action.

  • I'm also on Silverbullet, and from OP's description it sounds like it could be a good fit. I don't use any of the fancy template stuff - just a bunch of md files in a directory with links between them.

  • Your workload (a NAS and a handful of services) is going to be a very familiar one to members of the community, so you should get some great answers.

    My (I guess slightly wacky) solution for this sort of workload has ended up being a single Docker container inside an LXC container for each service on Proxmox. Docker for ease of management with compose and separate LXCs for each service for ease of snapshots/backups.

    Obviously there's some overhead, but it doesn't seem to be significant.

    On the subject of clustering, I actually purchased three machines to do this, but have ended up abandoning that idea - I can move a service (or restore it from a snapshot to a different machine) in a couple of minutes which provides all the redundancy I need for a home service. Now I keep the three machines as a production server, a backup (that I swap over to for a week or so every month or two) and a development machine. The NAS is separate to these.

    I love Proxmox, but most times it get mentioned here people pop up to boost Incus/LXD so that's something I'd like to investigate, but my skills (and Ansible playbooks) are currently built around Proxmox so I've got a bit on inertia.

  • Is that a mini? I love those little 1L HP's. I run 3 G2 800's. These are very nicely built and therefore a joy to work on, and sip power when idling. Highly recommend. Also +1 for Proxmox.

  • For light touch monitoring this is my approach too. I have one instance in my network, and another on fly.io for the VPSs (my most common outage is my home internet). To make it a tiny bit stronger, I wrote a Go endpoint that exposes the disk and memory usage of a server including with mem_okay and disk_okay keywords, and I have Kuma checking those.

    I even have the two Kuma instances checking each other by making a status page and adding checks for each other's 'degraded' state. I have ntfy set up on both so I get the Kuma change notifications on my iPhone. I love ntfy so much I donate to it.

    For my VPSs, this is probably not enough, so I am considering the more complicated solutions (I've started wanting to know things like an influx of fali2ban bans etc.)

  •  
        
    - fiction
        - Abbott, Edwin A_
            - Flatland
                - Flatland - Edwin A. Abbott.epub
                - Flatland - Edwin A. Abbott.jpg
                - Flatland - Edwin A. Abbott.opf
        - Achebe, Chinua
            - Things Fall Apart
                - Things Fall Apart - Chinua Achebe.epub
                - Things Fall Apart - Chinua Achebe.jpg
                - Things Fall Apart - Chinua Achebe.opf
    
      

    So in each directory that I use to delineate a library, I have a subdirectory for each author (in sort order form). Within each author subdirectory is a subdirectory for each book, with just the title, then the book with (edit - the anti-injection code mangled how I was trying to say the book file name. it's [book name]-[author].[extension])

    I didn't invent this, it's just what Calibre spits out. When I buy a new book, I ingest it into Calibre, fix any metadata and export it to the NAS. Then I delete the Calibre library - I'm just using it to do the neatening up work.

  • If this is a question about how to access your server at home from devices anywhere, securely, with a simple setup, then the answer is turn off all that port forwarding, and use Tailscale.

  • With a somewhat similar usecase, I ended up using Kavita.