thirdBreakfast

@thirdBreakfast@lemmy.world

This profile is from a federated server and may be incomplete. Browse more on the original instance.

thirdBreakfast,

E. Jean Carroll could buy it off them for the lols.

thirdBreakfast,

Yep, shoutout to the contributors, they are certainly not dragging their feet on all these bugfixes.

‘My whole library is wiped out’: what it means to own movies and TV in the age of streaming services (www.theguardian.com)

*What rights do you have to the digital movies, TV shows and music you buy online? That question was on the minds of Telstra TV Box Office customers this month after the company announced it would shut down the service in June. Customers were told that unless they moved over to another service, Fetch, they would no longer be...

thirdBreakfast,

Wish by Peter Goldsworthy. J.J. has always been more at home in Sign language than in spoken English. Recently divorced, he returns to school to teach Sign. His pupils include the foster parents of a beautiful and highly intelligent ape named Eliza.

thirdBreakfast,

I run two local physical servers, one production and one dev (and a third prod2 kept in case of a prod1 failure), and two remote production/backup servers all running Proxmox, and two VPSs. Most apps are dockerised inside LXC containers (on Proxmox) or just docker on Ubuntu (VPSs). Each of the three locations runs a Synology NAS in addition to the server.

Backups run automatically, and I manually run apt updates on everything each weekend with a single ansible playbook. Every host runs a little golang program that exposes the memory and disk use percent as a JSON endpoint, and I use two instances of Uptime Kuma (one local, and one on fly.io) to monitor all of those with keywords.

So -

  • weekly: 10 minutes to run the update playbook, and I usually ssh into the VPS’s, have a look at the Fail2Ban stats and reboot them if needed. I also look at each of the Proxmox GUIs to check the backs have been working as expected.
  • Monthly: stop the local prod machine and switch to the prod2 machine (from backups) for a few days. Probably 30 minutes each way, most of it waiting for backups.
  • From time to time (if I hear of a security update), but generally every three months: Look through my container versions and see if I want to update them. They’re on docker compose so the steps are just backup the LXC, docker down, pull, up - probs 5 minutes per container.
  • Yearly: consider if I need to do operating systems - eg to Proxmox 8, or a new Debian or Ubuntu LTS
  • Yearly: visit the remotes and have a proper check/clean up/updates

RFK Jr. Swears He Wasn’t Thirsty for Fitness Influencer on TikTok (gizmodo.com)

The reply happened in Sept. 2022 on Tyler Idol’s account, which she now has pinned to her page, and was unearthed by some right-wing dork on X Wednesday. The reply is now deleted, but according to saved recordings, it simply stated “Wow” and was accompanied by two smiling faces with hearts emoji. As for how you can tell it...

thirdBreakfast,

I’m on board with original punctuation going inside the quote, but then to be consistent, capitalization has to as well. So instead of “This comment…” it should be “this comment…” since in the original quote that was just a clause separated by a comma, not its own sentence.

thirdBreakfast,

The Debian thong made me laugh. Who is buying this? For themselves, their partners? I’m imagining Christmas morning when I’m trying to explain the value of this gift you’ve just opened.

Network loss after 24hrs on Docker LXC

Fine folks of c/selfhosted, I’ve got a Docker LXC (Debian) running in Proxmox that loses its local network connection 24 hours after boot. It’s remedied with a LXC restart. I am still able to access the console through Proxmox when this happens, but all running services (docker ps still says they’re running) are...

thirdBreakfast,

No answer, but just to say I run most of my services with this setup - Docker in a Debian LXC under Proxmox, and don’t have this issue. The containers are ‘privileged’, and I have ‘nesting’ ticked on, but apart from that all defaults.

thirdBreakfast,

My ‘good reason’ is just that it’s super convenient - for backups and painlessly moving apps around between nodes with all their data.

I would run plain LXCs if people nicely packaged up their web apps as LXC templates and made them available on LXCHub for me to run with lxc compose up, but they generally don’t.

I guess another alternate future would be if Proxmox added docker container supervision to their web interface, but you’re still not going to have the self-contained neat snapshot system that includes the data.

In theory you should be able to convert an OCI container layer by layer into an LXC, so I bet there’s projects out there that attempt this.

https://lemmy.world/pictrs/image/68d09ae5-4a06-455b-9acb-249b8015b607.jpeg

thirdBreakfast,

There are a heap of general “Linux Administration” courses which will patch a lot of holes in the knowledge of almost all self-taught self hosters. I’d been using Linux for a while but didn’t know you could tab to complete file names in commands till I learned it on Udemy ¯_(ツ)_/¯

thirdBreakfast,

The two extremes:

  1. Keep it alive on ZFS with frequent scrubbing. Review best practice every couple of years in case it’s time to migrate it to holograms or whatever,
  2. Clay tablets.

Basic docker networking?

Hi guys! I’m going at my first docker attempt…and I’m going in Proxmox. I created an LXC container, from which I installed docker, and portainer. Portainer seems happy to work, and shows its admin page on port 9443 correctly. I tried next running the image of immich, following the steps detailed in their own guide....

thirdBreakfast,

I routinely run my homelab services as a single Docker inside an LXC - they are quicker, and it makes backups and moving them around trivial. However, while you’re learning, a VM (with something conventional like Debian or Ubuntu) is probably advised - it’s a more common experience so you’ll get more helpful advice when you ask a question like this.

thirdBreakfast,

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.

thirdBreakfast,

For anyone coming to this later, digests are not presented in a super-understandable way (there’s a good explanation of them in this stack-overflow). There appears to be two ways to get the digest that matches the one on the DockerHub page for the tag:

  • pull the image (what I was trying to avoid)
  • use API 2 (requires a token)

There’s a good discussion of options for finding out if images have been updated in this r/SelfHosted discussion which is what I was trying to achieve.

your favorite homelab applications

Hi, just recently it’s foss had an article about homelabs. Of course I digged in, since there is a small nuc working tirelessly in the corner of my routers closet. So far it just crawls some web pages for me and sends emails accordingly to my filters. So I hoped to find new exciting stuff to let it crunch through. The articles...

thirdBreakfast, (edited )
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}

thirdBreakfast,

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.

thirdBreakfast,

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.

thirdBreakfast,

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.

thirdBreakfast,

Oh no! This is a sad story.

thirdBreakfast,

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

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • kavyap
  • DreamBathrooms
  • cisconetworking
  • Durango
  • mdbf
  • magazineikmin
  • ethstaker
  • osvaldo12
  • rosin
  • Youngstown
  • slotface
  • everett
  • tacticalgear
  • megavids
  • thenastyranch
  • ngwrru68w68
  • modclub
  • cubers
  • normalnudes
  • InstantRegret
  • GTA5RPClips
  • tester
  • khanakhh
  • provamag3
  • anitta
  • Leos
  • lostlight
  • All magazines