thirdBreakfast

joined 1 year ago
[–] thirdBreakfast 2 points 2 weeks ago (3 children)

The process for this is to obtain an EPS32 with bluetooth and wifi, pair it to the scale with bluetooth then keep it powered on in range of the scale, then the data goes into HA?

[–] thirdBreakfast 6 points 3 weeks ago

I have the opposite experience of this. All of my local services are a single docker container inside an LXC. I don't like that it's conceptually messy, but in practice it's easy to manage. What I love about it is the simplicity of backing up or moving the entire LXC between servers.

I've not had any drama with things breaking across Proxmox updates. The only non-gui thing I need to do during the process is adding two lines to the LXC conf to have Tailscale work correctly.

[–] thirdBreakfast 3 points 3 weeks ago

Thanks for this. I appreciate you sharing the summary and some photos instead of just a link to your (excellent) review.

[–] thirdBreakfast 37 points 1 month ago (6 children)

It's mind-bogglingly convenient, especially compared to the before times. Consider donating to them if you can.

[–] thirdBreakfast 58 points 1 month ago

No one's mentioned Forgejo yet? Solid git and artifact repository.

[–] thirdBreakfast 7 points 1 month ago

+1 for the Seiko 5s. Love me a SNZG07J1

[–] thirdBreakfast 3 points 1 month ago (10 children)

There's lots of ways to skin this particular cat. My current approach is low powered Synology (j series?) for mass storage, then 1 litre PC's running proxmox for my compute power using their NVME for storage, all backed up to the Synology.

[–] thirdBreakfast 16 points 1 month ago (1 children)

Two good points here OP. Type docker image ls to see all the images you currently have locally - you'll possibly be surprised how many. All the ones tagged <none> are old versions.

If you're already using github, it includes an package repository you could push retagged images to, or for more self-hosty, a local instance of Forgejo would be a good option.

[–] thirdBreakfast 1 points 1 month ago (1 children)

Harold Holt just fucked off one day.

[–] thirdBreakfast 2 points 1 month ago

For the moment, I think the best advice is to learn Linux. If you want an "all in one place" approach to that, it would mean one of the Linux administration courses on Udemy, but there's also heaps of good beginner content on YouTube. I imagine by the time you got half way through the course and could spin up a VPS, point a domain name at it, and run things in Docker you'd be ready to shift your learning to the practical things you wanted to host then learn that way - by trying.

This has come up a few times on Lemmy and elsewhere, and I'd love us (the community) to come up with a better answer - some sort of "Self-Hosting for Dummies" starter document, but spanning the giant divide between the general overview and practical achievements, and then keeping it up to date would be a Herculean task.

[–] thirdBreakfast 1 points 2 months ago

Build anything small into a container on your laptop, push it to DockerHub or the Github package registry then host it on fly.io for free.

[–] thirdBreakfast 1 points 2 months ago

Photograph: Fredrik Varfjell/NTB/AFP/Getty Images

 

*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 able to access the films and TV shows they had bought. *

 

I've been thinking about writing a script that would alert me if there was an updated version of an image I was running.

DockerHub shows an image digest on the page for that tag:

And I can extract the digest for an image I am running with:

docker inspect --format='{{index .RepoDigests 0}}' jc21/nginx-proxy-manager:latest

This matches the one from the DockerHub screenshot. But I can't see a CLI way to get the image digest from a registry. It seems like:

docker manifest inspect jc21/nginx-proxy-manager:latest

should do it, but it pulls out the digest of each of the architecture builds for that tag instead of the one shown in dockerhub.

Is there a way to compare the current local image with one in a registry from the command line? Or perhaps there's a more sensible way to do this?

 

I'm currently brewing in an Aeropress, and considering one of the lower end espresso machines.

But based on a few comments from James Hoffmann about him drinking filter coffee at home, I'm wondering if an espresso machine is something that people end up using every day, or if people are brewing with simpler methods and just making espressos when they've got time on the weekend or people over?

What's your experience, did you buy a machine and it mostly just takes up counter space, or is it a daily source of joy?

 

Somewhat bewildered by the millions of Aeropress recipes on youtube, I'm wondering if daily users end up settling into a reliable, simple process that's similar from person to person.

In particular, I note that my method (basically a french press) is vastly different from the one in the instructions which is ground much finer, uses less water, and starts dripping through the filter immediately.

Anyway, here's me:

  • 12g mild-roast (coarse ground a touch finer than most people would use for a french press, done with a C2)
  • inverted
  • one filter paper, not washed, but damp enough to stick
  • fresh boiled water (so probs 95°+) 180g
  • stir enough to break up the floaties
  • push the plunger in far enough that the liquid is almost at the top before I put the filter on
  • tip over and start plunging at 1:30, finish by 2:00
  • into ~70g warmed milk

I'd love to hear yours.

 

Moved from a Rhinowares to a 2021 Timemore C2, stumbled out to breakfast and used the same clicks without thinking.

 

I'm a coffee newb - bought an Aeropress and a Rhino hand grinder, and I've sort of flailed around changing things randomly and ended up with an enjoyable repeatable cup by sticking to the same beans, grind, water temperature, brew time & method that seems to work for me.

My issue is I'm not really sure about the terms used to describe the basic aspects of coffee taste - eg bitter, sour, acidic, under extracted, over extracted, etc. I feel like if I did understand them, that would give me the skill to try different things (such as a different roast) and adjust the other factors to match them to get something that suits me, or to be able to make a cup of coffee that would suit someone else's taste.

I'm wondering if you're able to tell me how to deliberately create these other tastes - I imagine I could comparatively taste them and mentally match the words to the sensations. For example, how can I deliberately create an obviously bitter cup, an over extracted cup etc.

The resources I've got for this project are the Aeropress and grinder mentioned, Nespresso machine, a medium and a dark roast, a French Press, and whatever coffee I can get from a supermarket.

Does this sound like a viable plan? If so, what are the tastes I should learn, and how can I create guaranteed and slightly exaggerated versions of them?

 

I started on Elitedesk 800 G1s when Raspberry Pis got hard to find and expensive, and I now feel they are better in every respect if you don't need the GPIO pins.

Every time I open them up to upgrade something I'm impressed with the level of engineering. There are quality manufacturer manuals for them, the cooling is good and they look great

 

The P20iX is a tacticool type 21700 size light. It's very floody - perfect for inside buildings or close range outside where you need a big field of view, and bright enough at 4000 lumens .

The bumps on the front are something super tough for breaking car windows etc - so I guess aimed at first responder types. I quite like the double clicky tail switch. One is a really solid on/off click and the other cycles between light levels.

It has two modes, I use it in the everyday mode where it remembers the light brightness from when you turned it off. There also a hard core mode where it always turns on in max.

The hard plastic holster has a hole in the bottom, which I assume is to avoid melting it with the 4 x 4 x CREE XP-L2V6 leds, but I have occasionally just turned it on in the holster for general lighting if I needed both hands.

Since it's quite easy to pull it out of the holster, I do have a slight worry that it will come out by itself if I'm clambering around somewhere - but it never has yet. The holster is intended for clipping on those massive duty belts - it would swing around a bit otherwise. I have a vague recollection it came with some clips to use on narrower belts but perhaps I've thrown them away.

The 21700 battery it needs is a weird Nitecore one with positive and negative contacts each end. I wasn't wild about that, but in practice I never carry spare batteries, so they can be weird or built in and it's no particular problem. If you really hate this idea, there is an optional caddy for 2 x cr123s - but less brightness and lower run times.

 

The RovyVon A5x is my EDC at the moment, and I love it enough that I bought another one when I killed it in the washing machine (it's IP66 - but only with the charging plug in - long story at the end).

Like a few of these little lights, it has ancillary LED's on the side. I chose the white+UV side LEDs. The other option is white + red which would probably be more useful, except this is the glow-in-the-dark case, and the UV supercharges that in a couple of seconds.

The GITD is not amazing, but if you're camping away from city lights, it's still bright enough to find the next morning right up till the sun comes up.

The choices for the main LED are CREE XP-G3 or Nichia 219C. I went with the Nichia with a warmer CRI. The Nichia is 450 lumens vs the Cree 650.

The battery is rated 330mAh and is USB-C chargeable (I think my old one was mini USB?). The story with the charging plug on my old one was I washed it in the pocket of some pants, and it still worked, but I could see a drop of moisture inside. I pulled the charging port stopper right out since it kept half closing itself in the rice. Then I couldn't get it back in (probably could have with tweezers) so I thought I'd do that later, then washed it again the following weekend without the plug in. I went all out with the drying attempts, but it was properly soaked through, and never came back from that.

It doesn't really tailstand unless you've got the magnet on (I do) and something to stick it to. It's just a lovely little general use torch for your pocket.

reflector view

 

I own, and often carry, a lot of lights. The i1R2 probably hasn't got the most hours on it, but in terms of the number of times it gets turned on, it's by far the winner.

 

I've EDC'd something like this for about sixteen years. This is the RovyVon Aurora A5 (G3)-UV + White with the Nichia 219C LED. I mostly just use the UV to give the glow in the dark case a little charge as I'm dropping it on the nightstand.

It's not my first A5 - I've killed one in the washing machine. I replaced that one with a Fenix E05R which is way more washing machine proof, but I just never had the same love for it as I do for the A5.

Before those, for many years it was the Fenix LD01 - mine has that wonderful beat up look you only get from using a light every day for years.

There's also been a number of no-name 10440 lights that I seem to lose more easily than the brand name ones :-/

In the same pocket is an Olight i1R 2 on my keys - so it also has the 'well worn' look.

 

I've been downloading SSL certificates from my domain provider, using cat to join them together to make the fullchain.pem, uploading them to the server, and myself adding a 90 day calendar reminder. Every time I did this I'd think I should find out about this Certbot thing.

Well, I finally got around to it, and it was one of those jobs which turns out to be so easy you wish you'd done it ages ago.

The install was simple (I'm using nginx/ubuntu).

It scans up your server conf files to see which sites are being served, asks you a couple of questions, obtains the Let's Encrypt certificate for them, installs it, updates your conf files to use it, and sets up a cron job to check if it's time to renew the certificate, which it will also do auto-magically.

I was so pleased with it I made a donation to the EFF for it, then I started to think about how amazingly useful Let's Encrypt is, and gave them one too. It's just a really good time to be in this hobby.

I highly recommend Certbot. If you've been putting this off, or only just hearing about it, make some time for it.

view more: ‹ prev next ›