dokku-letsencrypt VS heroku-buildpack-ruby

# 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:

Did you find this article? https://github.com/heroku/heroku-buildpack-ruby/issues/1202

There is a Github issue on this topic in the heroku-ruby-buildpack repo with some success stories in the comment section and a hint that build-in-app-dir may become the default behaviour in the future.

For instance the way Heroku used to build apps defeated a good part of Bootsnap usefulness, actually making it slow boot time, but they fixed that recently https://github.com/heroku/heroku-buildpack-ruby/issues/979.

{ "environments": { "test": { "buildpacks": [ { "url": "https://github.com/heroku/heroku-buildpack-ruby" }, { "url": "https://github.com/heroku/heroku-buildpack-chromedriver" }, { "url": "https://github.com/heroku/heroku-buildpack-google-chrome" } ], "addons": [ "heroku-postgresql" ], "scripts": { "test-setup": "bin/rails assets:precompile", "test": "bin/rspec" } } } }

{ "env":{ "RAILS_MASTER_KEY":{ "require":true } }, "scripts":{ "postdeploy":"bin/bundle exec rake db:migrate rake db:seed" }, "addons":[ { "plan":"heroku-postgresql:free" }, { "plan":"heroku-postgresql:free", "as":"audit" }, { "plan":"rediscloud:free" }, { "plan": "rollbar:free" } ], "buildpacks":[ { "url":"https://github.com/heroku/heroku-buildpack-ruby" } ] }

This answer might help you OP, schneems says (in 2017 mind) that you need to manually define the missing assets:precompile task.