Josh Holbrook

You should be able to `require('./')` without getting db lock errors. Calling builder.init() should set up the db on the cache layer.

upgrade to npm@3

6

We should run npm dedupe for moar smallers bundles.

refactor to have separable build servers

1

I think the end architecture should look something like, ``` --->(Actual Real CDN)--->(app-level cache/lookup)--->(gearman server)--->(builder workers) ``` The CDN can only cache specific routes. The app-level cache/lookup is still required...

Sure would be nice if we could see which version of browserify wzrd.in was running when shit breaks!

Prereq for #62. Also useful build information.

https://gist.github.com/kumavis/7be352f3b61cc0846285

issues involving libraries that use request and/or the dns module

2

https://gist.github.com/maxogden/d3353cfaa66eabe5d18c https://friendpaste.com/4hvzoL2l8p8kQjoyQidU3G Also interesting is that it happily spat out 80% of the code. Perhaps the error messages shouldn't include the bundled stdout? Unsure.

This will let me create multiple browserify-cdn instances, which would be pretty sweet.

Use s3 to store builds and redirect to the build server if no key.

This fixes npm2nix so it will run against the current npm registry. Without it I get a mess of 401s. Note that npmconf is deprecated, and that in the future...