node-canvas 1.0 is out

[hampelm]

I just noticed that node-canvas 1.0.1 was released late February. Unclear how much actually changed, but there might be something useful here?

[hampelm]

Need to evaluate in the context of #29

[Mr0grog]

I believe our big sticking point before was some issue with anything newer than node-canvas~0.12 on Heroku. We should take a look at https://github.com/bloomtime/heroku-buildpack-nodejs/tree/cairo and see if that works. I not, spend some time looking into buildpacks and see if we can fix it.

[Mr0grog]

Oh, guess that's also semi-detailed in #14.

@hampelm, @eddietejeda, how important is Heroku support to you guys? Is it worth worrying about in the context of this?

/cc @bensheldon since this was originally a major concern from him.

[prashtx]

Heroku support is pretty important for me and @hampelm. We'd like to avoid hosting this on our own EC2 servers, and this will be hosted , not just local.

[eddietejeda]

Agreed. Heroku is important to me as well.

Eddie A Tejeda

On Friday, March 22, 2013 at 1:21 PM, Prashant Singh wrote:

Heroku support is pretty important for me and @hampelm (https://github.com/hampelm). We'd like to avoid hosting this on our own EC2 servers, and this will be hosted , not just local.

—
Reply to this email directly or view it on GitHub (#43 (comment)).

[bensheldon]

FYI, seems like a new build is working on heroku:

Automattic/node-canvas#114 (comment)

bloomtime/heroku-buildpack-nodejs#1 (comment)

[deedubs]

Using the buildpack mentioned above this is https://github.com/codeforamerica/nodetiles-init using [email protected] on [email protected]

http://guarded-chamber-9870.herokuapp.com/

[Mr0grog]

Thanks for testing this out and prompting me to get my but in gear, @deedubs!