Using Fabric and Git to manage Heroku environment configuration.
As previously discussed YunoJuno runs on Heroku. Doing so means adopting
their 12-Factor App philosophy, which has worked out great for us, and makes the project very clean in terms of separating code from configuration. One of its core tenets (and a requirement for hosting apps on Heroku) is the use of environment variables to store . . .
How we roll
As a gentle introduction to our blog, I thought I'd begin with a brief outline of our technology stack.
We have already published a colophon detailing our stack, and we also publish our git commit log as a changelog, but we will be using this blog as a longer form narrative around our working practices, the tools we use (and how), and . . .
One the great things about setting up YunoJuno is that I've got to see a
lot of freelancer profiles.
We personally validate every application that
we get, which means that the information that we receive from freelancers
registering on the site is critical - it's the 'shop window' for anyone
joining our community. We've . . .
Using Fabric to automate pretty much everything
If you are a python developer and you don't already use Fabric, then you should. I can't imagine working without it.
When we started out on the YunoJuno journey we built a prototype, and deployed it. It worked. We deployed it to Heroku, which made things easy for us, as a deployment is really just a
git push. Well, it's a
git push . . .
Inspired by Etsy's 'Code as Craft', and built by humans, this is where we will be posting articles on tech as seen by the YJ team. This will be opinionated and personal, but hopefully also useful.
We're only starting out, so aren't going to be pushing too many envelopes at the moment, but if you're interested in . . .