I have Jekyll setup (not recommended, see below) to generate my sites in a Docker container. The builder container outputs my websites into a volume that's shar

I have Jekyll setup (not recommended, see below) to generate my sites in a Docker container. The builder container outputs my websites into a volume that's shared with nginx. I have shared assets for multiple websites and had to create a custom plugin to support this setup in Jekyll: https://github.com/sumdog/jekyll-multisite https://github.com/sumdog/jekyll-multisite There are open issues and pull requests for the plugin. I started building a test suite so I could start doing tests against multiple Jekyll versions and make it more universal, but it currently fails tests even with the same Gemfile/lockfiles. Currently I have to keep my site pegged to Jekyll 3.0.1 because of all the custom plugins I've written, and think Jekyll-multisite might be tied directly to my build. :( I've put little effort into it lately since Jekyll themes are suppose to address the multi-site capabilities. I just keep it building a a docker container so I can use the older version without trouble. I have that nginx container running behind the official HAProxy container and have Certbot running in its official container as well. I have a guide on how to set this up including all the Dockerfiles on github that you can use and modify: http://penguindreams.org/blog/bee2-automating-haproxy-and-letsencrypt-with-docker/ http://penguindreams.org/blog/bee2-automating-haproxy-and-le... As you can see, my blog isn't on the new setup yet (no https/letsencrypt). I'm working on that though, and hope to have it all migrated over this week. I would NOT recommend Jekyll if I was starting again. I had to do a lot of hacking and custom ruby coding to get really basic things I wanted working. Under the shell of Jekyll is a huge mess. It likes to iterate over things .. a lot .. all the time, for everything. Lots of the path resolution stuff is broken and lots of Jekyll is built around github pages, making some things impossible without violating the security model.