<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Github on zzamboni.org</title><link>https://zzamboni.org/tags/github/</link><description>Recent content in Github on zzamboni.org</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>diego@zzamboni.org (Diego Zamboni)</managingEditor><webMaster>diego@zzamboni.org (Diego Zamboni)</webMaster><copyright>© 2026 Diego Zamboni</copyright><lastBuildDate>Tue, 16 Apr 2019 11:25:00 +0200</lastBuildDate><atom:link href="https://zzamboni.org/tags/github/index.xml" rel="self" type="application/rss+xml"/><item><title>Automating Leanpub book publishing with Hammerspoon and CircleCI</title><link>https://zzamboni.org/post/automating-leanpub-book-publishing-with-hammerspoon-and-circleci/</link><pubDate>Tue, 16 Apr 2019 11:25:00 +0200</pubDate><author>diego@zzamboni.org (Diego Zamboni)</author><guid>https://zzamboni.org/post/automating-leanpub-book-publishing-with-hammerspoon-and-circleci/</guid><description>&lt;p&gt;I am the author of two books: &lt;a href="https://cf-learn.info/" target="_blank" rel="noreferrer"&gt;&lt;em&gt;Learning CFEngine&lt;/em&gt;&lt;/a&gt; and &lt;a href="https://leanpub.com/learning-hammerspoon" target="_blank" rel="noreferrer"&gt;&lt;em&gt;Learning Hammerspoon&lt;/em&gt;&lt;/a&gt;, both self-published using &lt;a href="https://leanpub.com/" target="_blank" rel="noreferrer"&gt;Leanpub&lt;/a&gt;. The source of my books is kept in GitHub repositories. In this post I will show you how I use the &lt;a href="https://leanpub.com/help/api" target="_blank" rel="noreferrer"&gt;Leanpub API&lt;/a&gt; together with &lt;a href="https://www.hammerspoon.org/" target="_blank" rel="noreferrer"&gt;Hammerspoon&lt;/a&gt; and &lt;a href="https://circleci.com" target="_blank" rel="noreferrer"&gt;CircleCI&lt;/a&gt; as part of my workflow, to automate and monitor the building, previewing and publishing of my books.&lt;/p&gt;</description></item><item><title>Hosting a Ghost Blog in GitHub - the easier way</title><link>https://zzamboni.org/post/hosting-a-ghost-blog-in-github/</link><pubDate>Fri, 25 Aug 2017 09:00:00 +0200</pubDate><author>diego@zzamboni.org (Diego Zamboni)</author><guid>https://zzamboni.org/post/hosting-a-ghost-blog-in-github/</guid><description>When I was planning the reboot of my website, I seriously considered using Ghost. It has a very nice UI, beautiful and usable theme out of the box, and a very active community. Eventually I decided to use Hugo, but in the process discovered that it is possible to host a statically-generated Ghost website using GitHub Pages.</description></item><item><title>Using Multiple SSH Keys with Github</title><link>https://zzamboni.org/post/using-multiple-ssh-keys-with-github/</link><pubDate>Wed, 20 May 2015 00:00:00 +0000</pubDate><author>diego@zzamboni.org (Diego Zamboni)</author><guid>https://zzamboni.org/post/using-multiple-ssh-keys-with-github/</guid><description>&lt;p class="clip-attribute"&gt;via &lt;a href="http://www.freshblurbs.com/blog/2013/06/22/github-multiple-ssh-keys.html#tldr"&gt;http://www.freshblurbs.com/blog/2013/06/22/github-multiple-ssh-keys.html#tldr&lt;/a&gt;&lt;/p&gt;

&lt;span&gt;&lt;br/&gt;
&lt;div style='margin-left:40px;'&gt;Since Github doesn't allow us to reuse an SSH Key, the only sane solution is to jump through some hoops and generate + use multiple keys on the server itself. Let's look at some effective approaches of doing that.&lt;/div&gt;
&lt;div&gt;&lt;br/&gt;&lt;/div&gt;
&lt;div&gt;Short version: define multiple hosts in the SSH config file for each repository, which use different SSH keys, then you can assign different deploy keys to each repo. But read the whole article for the full details.&lt;/div&gt;
&lt;div&gt;&lt;br/&gt;&lt;/div&gt;
&lt;/span&gt;</description></item><item><title>Website redesign and unification</title><link>https://zzamboni.org/post/website-redesign-and-unification/</link><pubDate>Tue, 28 Sep 2010 02:22:09 -0500</pubDate><author>diego@zzamboni.org (Diego Zamboni)</author><guid>https://zzamboni.org/post/website-redesign-and-unification/</guid><description>There are still some rough edges, but by far the redesign and unification of &lt;a href="http://zzamboni.org/"&gt;zzamboni.org&lt;/a&gt; is done. With the same design you can now find my blogs (hosted by posterous.com), my project pages (hosted in github.com project repositories) and some static pages (hosted in my personal github.com pages repository, this includes the root, About and Code pages, as well as the static copy of my old blog &lt;a href="http://zzamboni.org/brt/"&gt;BrT&lt;/a&gt;, which is the only one that retains its original design). The theme is a variation of Posterous' "Paramaibo".&lt;p&gt;&lt;/p&gt;</description></item><item><title>cfengine Community Open Promise Body Library on GitHub</title><link>https://zzamboni.org/post/cfengine-community-open-promise-body-library-on-github/</link><pubDate>Wed, 25 Aug 2010 01:37:00 -0500</pubDate><author>diego@zzamboni.org (Diego Zamboni)</author><guid>https://zzamboni.org/post/cfengine-community-open-promise-body-library-on-github/</guid><description>&lt;p&gt;I have created a &lt;a href="http://github.com/zzamboni/cfengine-copbl"&gt;copy of the cfengine COPBL on GitHub&lt;/a&gt; , where I will use it as a playground for changes and additions. This is in no way endorsed by cfengine - it is just my personal copy. But if you use GitHub and want to use it, go ahead, I will try to keep it updated with respect to &lt;a href="http://www.cfengine.org/pages/develop"&gt;the original subversion repository&lt;/a&gt; , although it will include my changes too. &lt;/p&gt;</description></item><item><title>Updated server and service setup</title><link>https://zzamboni.org/post/updated-server-and-service-setup/</link><pubDate>Mon, 16 Aug 2010 14:58:00 -0500</pubDate><author>diego@zzamboni.org (Diego Zamboni)</author><guid>https://zzamboni.org/post/updated-server-and-service-setup/</guid><description>&lt;p&gt;(a friend asked me about my online setup, and I wrote the text below. Then I realized it would also make an interesting blog post, and I just copied and pasted it, with minimal editing, into an email to posterous. This is why I love posterous, it makes posting so easy) &lt;/p&gt;</description></item></channel></rss>