Hey, great work!

Similar to my project https://commits.io

Shoot me an email (ortuna AT gmail) if you want to compare notes. I've done a lot of work on how to get those generation times down.

Cool service! I had fun playing with the generator but have no intention of ordering a poster.

Recommendation: Allow users to generate an image and either share it on social media, or embed it in their blog. This way you at least get promotional value out of customers who do not intend to buy.

I would love to order a poster but I just cannot get over the whole -- exposing my teams private code to a 3rd party thing. Any chance you have a hosted version of this?

You could always write a script that walks the real commits of your repo and generates fake commits in a public repo with the same timestamps but no meaningful changes or commit messages.

Not yet, waiting for Github to add some fine tune permissions that would ease a lot of worry. You could always create a GIST with exactly what you're comfortable with.

Hi! Love your site. Always wondered, is it making any money?

it's doing well ;) but is equal to the time I put in.

Awesome, thanks ortuna! Definitely will do.

Queues are seriously backing up. Sorry about this!

My username wasn't found. Can you document and share the remedy to this? Might be a good source for scaling issues when posting to HN.

Renders are split out into their own queue now, so those should work pretty quickly. I'm having issues getting all the GH history, so please be patient on that. Sorry!

Can you set up an "email when its ready" feature?

Very cool! Simple and you even thought of a way to earn some money with it. Hope this kind of creativity gets rewarded!

Spoiler alert, it was ActiveRecord.

Not kidding.

Post definitely forthcoming!

What part of your process is the bottle neck? Are you rendering the posters server side?

From the page...

    [...] because I'm rendering actual JPGs server-side so that the prints will be identical to the previews. I could probably do it much faster if I did it all client-side with SVGs, but I went with what I already knew. Maybe v2.0 will be more awesome.

Thanks, I didn't see that.

Turns out every part of my process is the bottleneck, ha.

I'm fetching the user's history from GH, which is working OK at best right now, and also rendering them server side.

So... 0 for 2.

That's okay though. Only way to learn is by getting something out there. You're way ahead of the game compared to most people dealing with scaling issues first hand :)

Keep up the good work!

Thanks winslow. I appreciate you saying that

lambda would be a good way of scaling this without improving the architecture otherwise :)