ezinnit VS dokku-letsencrypt

for your domain to work, you need a DNS "A" record pointing your domain to your server ip address (create the DNS "A" record before running ezinnit)

your local machine's ssh key added to your new server's allowed hosts (digital ocean tutorial)

ezinnit

gitlab personal access token

# plugin installation requires root, hence the user change sudo dokku plugin:install https://github.com/dokku/dokku-letsencrypt.git

downloads and installs dokku-letsencrypt on server

$ sudo dokku plugin:install https://github.com/dokku/dokku-letsencrypt.git $ dokku config:set --global [email protected] $ dokku domains:set app-name your-domain.com $ dokku letsencrypt:enable app-name $ dokku letsencrypt:cron-job --add

You need SSL certificate for your website. With Dokku you can add it in several ways, using official Let's Encypt plugin, or using your own certificate, or using a Cloudflare SSL. Any of these do, but don't neglect this step.

There are env vars you need to configure so let’s encrypt knows your email address. The plugin docs are worth reading: https://github.com/dokku/dokku-letsencrypt

# on Dokku host sudo dokku plugin:install https://github.com/dokku/dokku-letsencrypt.git

Right now (when I wrote this post), there is no wildcard support from dokku-letsencrypt plugin. Luckily, Dokku itself can use certificates from other sources.

As you may have noticed, our application is available on our Dokku host now – but only in an unencrypted fashion (note the lack of https in the address bar). Thankfully, we live in the age of LetsEncrypt offering free TLS certificates, and Dokku makes it easy to enable automatic certificate retrieval and setup for our application via the dokku-letsencrypt plugin. I strongly recommend setting up this plugin so that people using our application can enjoy securely encrypted web-traffic. Once installed (see installation and initial setup instructions), we can enable the LetsEncrypt integration for our application with a single command: