Doesn’t seem mutually exclusive. Replace the docker rm with compose down and the docker run with compose up.
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.
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.
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?
deleted by creator