Blog

As a recipe, if you want to enable a custom domain name on blog-o-matic a special file needs to be created on the ‘GitHub Pages’ served ‘master’ branch. In order to do so, edit pelicanconf.py and add the following differences: diff --git a/pelicanconf.py b/pelicanconf.py index 680abcb..fc3dd8f 100644 --- a/pelicanconf.py +++ b/pelicanconf.py @@ -46,13 +46,16 @@ AMAZON_ONELINK = "b63a2115-85f7-43a9-b169-5f4c8c275655" # Extra files customization -EXTRA_PATH_METADATA = {} +EXTRA_PATH_METADATA = { + 'extra/CNAME': {'path': 'CNAME'}, +} + EXTRA_TEMPLATES_PATHS = [ "plugins/revealmd/templates", # eg: "plugins/revealmd/templates" ] -STATIC_PATHS = [ 'images' ] +STATIC_PATHS = [ 'images' , 'extra'] ## ONLY TOUCH IF YOU KNOW WHAT YOU'RE DOING! This will copy the CNAME file created in content/extra/CNAME to the resulting ‘master’ branch as /CNAME. ...

Introduction For some time now, I wanted to put the presentations I did in the past to be available, and since I’ve added support to my blog to render revealjs slides, I wanted to also put other presentations that I did in the past, probably (or for sure) outdated, but that were sitting in my computer drive. The presentations already got several transformations, but in the actual status they are stored as LibreOffice ODP files, that made it a bit difficult. ...

Introduction After my recent talk about blog-o-matic, I was trying to upload somewhere the slides I used. Since some time ago I started using Reveal-MD, so I could use Markdown to create and show slides, but wanted also a way to upload them for consumption. Pelican-revealmd plugin seemed to be the answer. It does use pypandoc library and ‘pandoc’ for doing the conversion. The problems found After some test, it had 3 issues: ...

Introduction I’ve already covered some articles about automation with Travis-CI, GitHub, and one step that seems a show-stopper for many users when trying to build a website is on one side, the investment (domain, hosting, etc), the backend being used (WordPress, static generators, etc)… While preparing a talk for a group of co-workers covering several of those aspects, I came with the idea to create Blog-o-Matic, implementing many of those ’learnings’ in a ‘canned’ way that can be easy to consume by users. ...

OSP Director OSP Director (or upstream TripleO) is a life-cycle manager for OpenStack based on the idea of using ‘OpenStack’ to deploy ‘OpenStack’. To do so, it creates a management ‘Undercloud’, that is configured and prepared for later deploying an ‘overcloud’ which is the one that will later run the workloads. TripleO/Director, also automates the inspection of hosts and tagging to the roles they will perform later in the ‘overcloud’ setup, such as ‘controller’, ‘compute’, ‘storage’, or even mixed roles via composable-roles support. ...