https://abhi.keybase.pub/2016/02/15/git-and-keybasefs.html
The general gist is that keybase.io is promising that it will only serve data at abhi.keybase.pub that has been signed for by that user.
11–20 of 98 posts
https://abhi.keybase.pub/2016/02/15/git-and-keybasefs.html
The general gist is that keybase.io is promising that it will only serve data at abhi.keybase.pub that has been signed for by that user.
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-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.
I run https://blog.jeaye.com/ on Github Pages, but I manually build with Jekyll locally, with a publish script, and then force push the built site + assets to the gh-pages branch. This allows me to use all sorts of Jekyll plugins which Github won't whitelist. I'm currently writing a post detailing how all of this works, for anyone interested.
git subtree push --prefix build origin gh-pages
is a nice simple way to push your build directory to the gh-pages branch.I wrote one a while back. It uses git, webhook to auto publish blog posts. Here's the git repo https://github.com/snehesht/blog
* Kickstarted in 2013
* Markdown-based
* Open source, self-hostable
* Hosted solution (https://ghost.org/pricing/) with support for your own domain name
* Beautiful themes out of the box with custom css/js on an article, site-wide or theme level
* Third party static site generation tools (https://github.com/axitkhurana/buster/, https://github.com/lexoyo/static-ghost)
Example blog (default theme): https://blog.ghost.org/
Jekyll really does give you full control. It also powers some pretty large websites. Breitbart.com and Forthepeople.com (shameless plug) spring to mind.