Back
t: 01474 704400 | e: [email protected]

Using Mercurial with Amazon OpsWorks

If you're not using Git then you won't be handed built-in repository management on a silver platter. Here is how to use Mercurial instead.

 
20/08/2014
If you're not using Git then you won't be handed built-in repository management on a silver platter. Here is how to use Mercurial instead.
Simon Hooker, Head of Product Development

So you have decided to use OpsWorks for your nice shiny cluster. This isn’t a bad plan, I’ve been using it to set up a new cluster and so far it has turned out ok. There is one minor issue though. As with many of these lovely services, if you’re not using Git then you won’t be handed built-in repository management on a silver platter. This is unfortunate because I (and it seems everyone I know that has tried it) prefer Mercurial.

While there’s not a lot you can easily do to allow managing your custom Chef recipes on Mercurial (just give up and use Git for this purpose) thankfully there are alternatives to just using Git for source control within OpsWorks. Admittedly I feel like I may have cheated a little bit but it allows use of Mercurial on OpsWorks without a lot of hassle with custom recipes so I’ll count it as a win.

Assumptions

  • You have already configured a Stack with a suitable Layer within OpsWorks
  • You are using BitBucket (or are happy to do so)

How to configure an App to use a Mercurial repository

  1. Push your Mercurial repository to Bitbucket. If you like you can keep the repository private
  2. Open up your project and go to “Downloads”
  3. Click on the “Branches” tab
  4. Find the branch you want to deploy to OpsWorks and copy down the corresponding zip file location
  5. Open your stack within the AWS console
  6. Click on “Apps”
  7. Click on +App
  8. Specify the following settings:

    – Repository type = Http Archive

    – Repository URL = The URL you found in step 4

    – User name / Password = If the repository is private, enter a valid Bitbucket user to allow access

  9. Fill out all other details as you wish (name / domains etc)
  10. Deploy!

That’s all there is to it. This won’t allow the app to automatically update when you push more updates to Bitbucket but will at least allow you to get started with a Mercurial repository on OpsWorks.

If you liked reading this article you may also like:

What happens next? Post launch activities Launching a website is an important milestone for any business, but the work doesn't stop there. In this infographic we outline key areas to keep on top to ensure ongoing performance. Communicating your school story on your website In order to provide a distinctive and memorable school website experience, it is essential that you communicate your school's story. In this blog post, we share our thoughts on how to best stand out online. Communicating through website photography and video Photography and video have the ability to really strengthen your school website experience, creating an emotional connection with the user. In this interview, we asked expert, Andy Catterall, his views on on the importance of good photography and video on the school website.