deploys What actually goes on during a deploy Previously, I covered, at a high level, how our builds work and what tools we used. I wanted to explain what exactly we are doing during a deploy, with an emphasis on tracking state. It’s one area where there aren’t a lot of good off-the-shelf tools
python How We Deliver Features to Pinners Previously we discussed what tools Pinterest uses for deploys [https://blog.dadops.co/2013/10/06/tools-we-use-to-release-pinterest/]. This article shows how we connect them to create a “pipeline.” In practice, Pinterest is a continuous delivery shop. That means at any given time we can serve
deploys Tools We Use To Release Pinterest We have a fairly flexible Continuous Delivery system at Pinterest. The tools we use are fairly accessible, so you can build your own Continuous Delivery system too. * Github Enterprise [http://enterprise.github.com/] is our version-control overlay. It manages code-reviews, facilitates code-merging, and most importantly has a
jinja DRY with Jinja Templates Jinja [http://jinja.pocoo.org/] is a great templating language that's used with Python. One of the easiest ways to not repeat yourself in Jinja is to use macros. Let's say you want to build a blog. You may want a blog that makes HTML like
mozilla Using git to borrow from the future One of the great features of git is the ability to re-order commits, break commits into parts, and merge commits together. Assuming that my master branch is a pristine copy of the site and an ancestor of mybranch we can re-order commits by running: git rebase -i master
database Database versus files for Images Update 2 January 2021: This was written in 2009 when virtual private servers were the rage, so I've updated it slightly to deal with our new cloud overlords. -------------------------------------------------------------------------------- Where should uploaded assets go? A habit I once had was to store the uploaded content (including images) in a
