[heretohelp]

The problem is that a lot of it is hacky and somewhat specific to our site. Not necessarily generalizable.

I will say this though, I've been using Fabric for a very long time and abuse it with glee.

Are there any dev-opsy/provisioning/whatever type pain points you'd like a blog post or exposition on?

Edit: I'm the CTO. I'm open to open sourcing our stuff, but the lack of generalizability makes it less than useful. There's an abundance of magic in our stack that automates everything. Idempotence was a core design goal.

Edit2: For local development, I automate everything surrounding the python packages and the virtualenvs for the various repos we have as well. It's pretty damned handy.

[clicks]

Sure, write on a generalized approach for deploying a Flask app with Fabric, virtualsenvs, and whatever else you use.

[heretohelp]

I'll see if I can distill what I've learned so far. It'd be a pretty boring/long post though.

[clicks]

Great, I'll be looking forward to it. Cheers!