News for hackers. Stuff that matters.
Re:The NYT's Visual Election Outcome Explorer - How we made ... by paulgb on Monday November 05, 2012 @01:37PM (#4745074)
> We use a git-backed preview server that allows us to share versioned previews of graphics (any commit, any fork) and get feedback.

I'm jealous that this exists and I didn't know about it. Anyone aware of something like this that exists in the open-source/SaaS world?

Re:The NYT's Visual Election Outcome Explorer - How we made ... by mbostock on Monday November 05, 2012 @01:57PM (#4745189)
It's mostly open-sourced, available here: https://github.com/mbostock/git-static
Re:The NYT's Visual Election Outcome Explorer - How we made ... by paulgb on Monday November 05, 2012 @04:29PM (#4745895)
Very cool. I love your work.
Re:The NYT's Visual Election Outcome Explorer - How we made ... by roryokane on Monday November 05, 2012 @01:53PM (#4745161)
GitHub supports that. Commits (on any branch) that change images display the images inline, and you can comment on those commits. Example commit: https://github.com/cameronmcefee/Image-Diff-View-Modes/commi...
Re:The NYT's Visual Election Outcome Explorer - How we made ... by mnutt on Monday November 05, 2012 @11:09PM (#4747215)
I actually ran into a very similar problem this weekend. I ended up using gitolite with post-commit hooks that checked out the repo to a directory served by nginx. It ends up taking up a lot more space than Mike's solution, but has fewer moving pieces, assuming you're already running nginx.

Additionally you can use it to set up some fancy rules, like the "production" branch push to a special place, allowing users to create their own repos, and fine-grained access controls via gitolite.

Re:The NYT's Visual Election Outcome Explorer - How we made ... by kkwok on Monday November 05, 2012 @02:04PM (#4745223)
This may be completely wrong. But is mbostock's http://bl.ocks.org/ an example of this? Makes sense, since he's one of the creators of the nytimes graphics as well.