Mina VS website

After that is ready just run the mina setup command and it will create mina’s folder structure for your project using the parameters you setup before. Read more info on mina setup on their Getting started guide.

However this model is generic to any client-server / monolithic / micro services approach and to any languages and frameworks. In my project I use Mina (Formerly using Capistrano), so that means that on each deployment the script makes a SSH-in to the remote machine and performs the deployment process: Git clone, Git pull, rake db:migrate assets:precompile, puma:restart, etc… Before using Capistrano I was doing all this manually #sigh.

Same with my experience. I could never get Capistrano to work. I blame the never updated documentation that also missing important details here and there so often. Reading the doc is like walking in the woods. In the end I switched to Mina, and finally everything works.

Not to be confused with Mina: blazing fast application deployment tool (https://github.com/mina-deploy/mina)

For production, use a proper certificate authority (e.g., Let’s Encrypt) instead of self-signed certs. Check out Let’s Encrypt for free certificates.

autocert is a Pomerium feature that automatically provisions and renews TLS certificates for your routes using Let’s Encrypt. No manual cert management, no copying files around — just tell Pomerium to handle it and it will issue valid certificates on the fly.

> speaking about it in webinars and various conferences

That's unfortunately the feeling I got from the landing page, lots of talking, bureaucracy and buzzword bingo and not much "doing".

I might be wrong. For comparison https://letsencrypt.org, not a single mention of "webinars" or "stakeholders".

Lets's Encript

The good news is that the times when SSL certificates were a luxury feature are gone. Let's Encrypt makes them available to everybody for free.

Let's Encrypt - Free SSL certificate authority

Create a local domain and generate SSL certificates for it using Let's Encrypt, and use it for my server.

Leverage existing trusted Certificate Authorities (Let’s Encrypt, DigiCert) or internal CAs for internal setups.

The ingress configurations in the cluster need to serve a certificate that is trusted by browsers and systems. One way could be registering a public (sub)domain for internal use, and use Let's Encrypt certificates, using DNS-01 challenge for verification.

One particularly helpful feature for beginners is Echo's ability to automatically handle TLS certificate installation using Let's Encrypt, simplifying the process of securing your web applications with HTTPS.