Putting it all together with virtualenv (and foreman)
(This is the final (possibly) article in a series of four, and follows on from Docker services. Code from this series of articles is available on Github as yunojuno/trifecta, and the VM is available on Atlas, the Vagrant box repository hosted by Hashicorp.)
If you've been following this series to date, you will now have a vanilla . . .
Upgrading the framework your entire website relies on is a hard job, but someone has to do it. It was my turn here at YJ: migrating from Django 1.7.8 to 1.8.2.
Here's the list of things that broke on the way. Many of them are documented in the release notes, some of them are not: they're probably quite niche and specific to . . .
Create your own Heroku-like addons
Following on from the previous article, we now have a Vagrant VM,running Ubuntu 14.04, with Python 2.7.9 installed, along with Virtualenv and Docker:. . .
Part one of the dev trifecta series
(This is the second article in a series of four - following on from Vagrant, Docker, Virtualenv - the dev trifecta. The next article in this series is now available - Docker services. Code from this series of articles will be made available on Github as yunojuno/trifecta.)
As discussed in the opening article, the base platform for . . .
Build yourself a local Heroku
(This is the first part of a four-part series. Part two is now available - Vagrant as the base OS)
Having your developers write code and run it in an environment that matches your production environment can prevent nasty surprises, but how can do this when your application is hosted on Heroku, and your company doesn't own a . . .
Sometimes contrib.auth just isn't enough
We run a number of working environments on Heroku - in addition to the live site we have dedicated UAT and DEV environments, a DEMO environment for the sales team, and since the recent Heroku pricing changes we're thinking about a spinning up a new environment per developer (so they can push feature branches to a public location for . . .
Episode IV: A New Hope
The easiest way to solve a problem is not to have it in the first place
Tao of Hugo
I've written a lot in the past about trying to get Docker to work within an unstable developer's environment: tl;dr the dynamic allocation of IP addresses to containers makes it bloody hard if you need to start / stop containers . . .