It's time for the long overdue final installment of our Capistrano 3 tutorial series. To recap the preceding parts have been:
This installment will provide a more 'real world' example of using Capistrano to deploy a Drupal website. This allows us to illustrate how you might tailor a Capistrano deploy script to your own website.
I once had an interesting conversation in the pub with an old colleague about future technology predictions that will come true in our lifetime (about 2080 I hope!). There were some interesting ideas put forward such as:
There are glimmers of the first of the above coming true after a lab grown burger made the news last year.
One of our clients is an online motorcycle clothing and accessories business called Mototo.com. Mototo.com is powered by Magento, the popular open source ecommerce solution. We've found Magento to be great to work with. It provides a huge amount of functionality 'out of the box' and allows you to build an enterprise level ecommerce solution relatively quickly and therefore cheaply.
A piece of bespoke functionality we created for Mototo.com was a dynamic 'Bestsellers' page.
Welcome to part two in our three part Capistrano 3 tutorial series. If you worked your way through part one then you should be all set to write your first Capistrano deploy script. The deploy script we'll create will be a "bare bones" script which simply moves files from an SVN tag to a folder on your Staging server.
Compared to part one this tutorial instalment is a walk in the park. Enjoy!
Welcome to Part 1 of my Capistrano 3 tutorial series. This post covers installing Capistrano and getting to the point where we can create our first Capistrano deploy scripts.
This will be a techie and complex post as the subject matter is not trivial. I am assuming that you have basic familiarity with Linux and the command line. It will definitely be worth persevering through this tutorial series though as once complete your deployment process will be far easier. This is the hardest part of the tutorial series, it does get easier!
And with that...let's begin.
Over the last few months I wrote an in depth tutorial series on using Capistrano. This covered:
Unfortunately about two months ago Capistrano version 3 was released which has made my tutorial somewhat redundant. You can't stand in the way of progress though so I've recreated the series for Capistrano 3.
This final instalment builds on what we've run through previously to demonstrate how you can tailor a Capistrano deploy script to fit your application. We've chosen a Drupal website as an example because:
When we get approached for quote requests we always do some due diligence on the company making the request. This generally takes the form of checking their recent accounts filed at Companies House and researching their website and wider online presence. There have been several occasions recently where I have checked out a company's website, seen they have a Twitter account, browsed to it on Twitter and simply thought 'Wow!'.
Part three of my four part Capistrano series covers adapting the Ruby based Capistrano deployment tool for use with LAMP websites. If you missed the previous instalments of this Capistrano series then you can read parts one and two via our blog. This is a monumentally techie blog post which isn't for the faint hearted!
OK, time for part two in my four part Capistrano series of blog posts. In case you missed it you can find part one here. This is a techie post aimed at experienced website developers so consider yourself forewarned if you read on.
I decided to write this post based on my own experience of trawling Google for help bending Capistrano to my will and finding the lack of a joined up advanced tutorial frustrating. Over the course of this and the next part in my Capistrano series I will write a detailed tutorial going from installation of Capistrano to being in a position to deploy your website using the 'cap deploy' command. There are other tutorials that achieve this but none that:
