key

A dailykos article about a rawstory article about an nbc article about a newsguard article about how misinformation arose from a fourth-hand account.

TL;DR: no clue

RIP

The archive is blurred out for me, but highlighting everything makes it readable.

Saying we’re too divided and in the same breath casting divisive blame is… Not even surprising anymore.

For that size and given it’s a pi, maybe just a cheap usb stick

I was not expecting that. Trump continues to shock.

So OP is one of the only 25 people who used it?

deleted by creator

Doesn’t seem mutually exclusive. Replace the docker rm with compose down and the docker run with compose up.

I primarily use groups by room and floor. Since I only ever use groups for voice, for individual lights I don’t worry about brevity. I usually describe the fixture they’re in or type of light. Like I have “Standing Lamp Top”, “standing lamp side”, “living room candle #”, “kitchen downlight #”. The only semi creative name I have is “Ziggy” for these sorta zigzaggy adjustable lamps.

You can try using openssl s_client -connect domain:443 to help debug what the issue is. Without your domain it’s hard to guess what specifically is causing a TLS issue.

Where did you get your certs? Do they match exactly the domain you’re using? Are they expired or self signed? Are your details in the double curly brackets all correct?

You can try to use ssllabs, check cipher compatibility with browsers and such… though I think that requires things are working to a certain level first.

I have oil heat too and I struggle to imagine how you would add a sensor to it. That tank is solid and thick, trying to get anything inside it is a horrible idea and trying to sense through the metal is going to be prone to problems. In the past I’ve just pointed a camera at the main gauge.

Keep at it!

19 has federation bugs. Mainly outgoing but I’ve also seen incoming federation gradually fail. Restart the docker container routinely (cron job) until fixes come out.

Your app and DB should be deployed together in the same datacenter to minimize latency between app and DB. Nothing should be hitting your DB besides your app and any etl tools if applicable. So latency to your DB shouldn’t be an issue.

If you need to add redundancy with a deployment in another region you should consider having separate environments between regions with totally separate data which allows you to better manage data protection/export regulations appropriately.

If that doesn’t work you’ll need a multi region database, a vendor with support for that such as aws rds would be the sanest method but you can always hack it yourself.

There’s other options but those require an architecture designed to be heavily distributed and that depends a lot on the nature of your application and you’d ideally hire an architect experienced in such deployments.

“cock box” they sound… Reputable.

I don’t know that I’d do multiple smart bolts. It’s nice to have one for letting people in without needing them to have a key but you only need 1 door with it for that. I have a Schlage smart lock on one door and a downside is the battery. It uses a bunch of AAs and dies often compared to most devices. Needing to manage batteries on half a dozen bolts sounds obnoxious.

When I got my house I found that next to none of my actual locks needed to be totally replaced, I could just repin most of them to get aligned on a new key. I did end up replacing a crappy one and replaced cylinder on another.

Simple door sensors that let you know when a door opens/closes solves a similar problem set. I feel like most people end up centralizing on one or two doors and then the others rarely get opened, making the smart bolts a bit wasteful. It won’t tell you if it’s unlocked but it’ll let you know which doors to double check before bed.

I pretty much unified on Schlage for smart and dumb locks so my main key is the Schlage key that came with my smart bolt. The app feature set is fine, it allows good management of pass codes. Big downside is the battery like I said, and the app never seems to warn me about it.

I wouldn’t use AppD’s node agent as a starting point unless you’re planning to use AppD. Which you shouldn’t unless you’re a big business still talking about future plans to move to the cloud.

Picking a random image from dockerhub isn’t the best for security or reliability. You’re better off sticking to official images offered by a large, well known project. There’s even an official node image https://hub.docker.com/_/node/

You can copy files into the docker image via a COPY in the dockerfile or you can mount a volume to share data from the host file system into the docker container at runtime.

How do I see it before I decide whether to install it? The tutorial says to go to the website and make an account to try it out… But the website most prominently has a link to that tutorial. I don’t see any way to make an account or even a login form at all on the website. Did something not get deployed when you went live?