key

Tragic that people are still falling victim to these hope-rot schemes. Had an experience with facilitated writing schemes with family members 20 years ago. From non-verbal to shockingly eloquent in no time! It’s a miracle, turns out they were a genius trapped with an inability to express themself! Oh isn’t it strange that some people just can’t facilitate with them and what they say/know changes with the facilitator? Oh well, but thankfully the facilitator can always tell you what is meant when they use uncommon abbreviations!

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

Looking at NASA and Webb sites it appears this is a poorly cropped version of pictures from over a year ago, not something new like the article claims.

Wear the garlic as a garland when you sleep. Make sure to explain to your help that it’s important and handcuff yourself so you don’t take it off in your sleep. It’s the only way to keep Dracula away.

I was just looking at ADR templates recently. Something I’m wishing we started doing years ago

deleted by creator

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

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.

After the experiment, yes. Poor thing.

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 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.

That’s pretty neat. Is there a forked version that adds ticket number as a mandatory first class citizen? Cause that’d be darn near perfect.

A cubicle or desk populated with toys that came from ThinkGeek

What year is it?

checks git blame

Oh… 2014. That checks out.

https://github.com/anderspitman/awesome-tunneling