Pelican
In this third installment of my No Hassle Blog Automation series, I remove the necessity for running any infrastructure of my own. Drone has been replaced with a hosted solution at CircleCI. Their support is amazing, and their circle.yml format made configuration easy. Take a look at the first and second installments of this series.
Requirements
There are a few requirements for this setup:
- Rackspace Cloud Account
- Cloud Files Container*
- Existing Pelican Blog
- GitHub Account
* This container should be configured to serve a static site.
Due to the difficulty in maintaining a full Jenkins instance, I have revisited the blog automation issue and have replaced Jenkins with Drone. Making use of a tool like Drone greatly simplifies the setup process and lowers the barrier of entry for this type of project.
Requirements
There are a few requirements for this setup:
- Rackspace Cloud Account
- Existing Pelican Blog
- GitHub Account
- Linux Administration Knowledge
You should also read my original article.
Managing a blog can be a hassle. Operating system updates, blog software updates, and server security take up tons of time. Don’t forget about scaling your blog if you get popular. Inspired by the Rackspace DevOps post on their new blog format, I’ve setup my own version using Pelican instead of Octopress.
Resources
This tutorial will assume you have two systems to manage your blog.
- Local Workstation
- Remote Server
The local workstation will be used to manage your blog posts, as well as uploading the content. This system will need git and Pelican installed.