key

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

Walkthrough how to solve a complex non-linear differential equation step-by-step. Each step should be incorrect and as you explain it you remove an item of clothing. Once you have no more clothes, for the next step you pour a glass of seemingly-milk from a labelless container. The glass sits there while you do another step and then you drink it and say “that’s good goat sperm”. Before you finish the equation, a doorbell rings. You go over to the front door, open it, and retrieve a package. As the camera follows you we can subtly see the sky is green. You place the package on a table and finish explaining the equation. After you’re done you open the package; it’s revealed to be a rubber mask of a politician of your choice. You say “it’s time to save our country” and put it on. The final shot is of you leaving the house. Give the film a French name.

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.

What’s that on the wall?

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.

That open water bottle is nerve-wracking.

“cock box” they sound… Reputable.

James Corden! Happy birthday James!

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?

No info? No source? Good way to get people to run your zero-day.

You could use an LDAP and/or Kerberos solution to centralize user management. Alternatively you could use ansible

Private DNS within your Lan and your choice of proxy to remap ports

Using IP and port to connect? Definitely not going far enough yet!

Unless you live somewhere with above-ground powerlines and wind. Biannual occurrence for me.

No I won’t because it’s irrelevant if it is the only factor or not. It’s the limiting factor. Please don’t engage in red herrings.

That article is utterly unconvincing. It just handwaves the finite nature of our material reality with a very weak appeal to “infinite” human creativity. And then the conclusion is that infinite growth is necessary because there’s no way to change the status quo of wealth hoarding. It’s just apologism for the very worst aspects of capitalism without a single iota of serious thought.