Continuous Integration

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 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. ...

Background Elegant theme for pelican has been undergoing a big change from individual-driven effort to community, as part of this, one of the tasks to accomplish, has been the decoupling from author blog to project site for documentation. As we wanted this process to be both automated and allowed us to demonstrate via eat-your-own-dog-food that the theme works and how it looks, the idea was to automate the rendering of Pelican website with new documents. ...