Broccoli and express.js about broccoli HOT 9 CLOSED

I don't think this is really feasible, since Broccoli has a broccoli build command that has nothing to do with the server. server.js also seems like a strange place to have the build definition for your app.

For what it's worth, I'm not overly concerned with having a bunch of files in the top-level directories of my apps. The actual complexity matters much more than the number of files.

from broccoli.

The scenerio I'm describing would fit very nicely into the app I'm currently building. I'm not saying that the command line is obsolete.

The idea is to have broccoli compile the scripts and assets when the server boots up. This is especially awesome if you deploy your server code using git. No command line calls needed.

from broccoli.

In my opinion people should not expose Broccoli to the world via a server, because you are adding a lot of attack surface just to serve a few static files. I've added this to the README too. Whatever quick hacks you do for your own apps is up to you (and totally reasonable), but I don't want to make this officially sanctioned.

from broccoli.

ember apps are great to serve from CDN's

from broccoli.

@joliss Broccoli basically generates files and stores them in a directory. Express takes those files and serves them. I don't see any danger in that. (With rebuilding disabled in production mode)
@stefanpenner CDNs are more for high traffic websites. For small sites having everything in one place is more convenient. But that's one of the things I really like about ember. The serverside complexity goes to zero.

from broccoli.

@MajorBreakfast - Not to quibble, but it is quite usual to generate static sites (whether with CDN or plain S3).

from broccoli.

@rjackson 'Course :) But throwing a little site on heroku is still easier.

from broccoli.

We should pave the static deployment path.

from broccoli.

Express takes those files and serves them. I don't see any danger in that. (With rebuilding disabled in production mode)

Hm yes, this doesn't seem unreasonable to support at some point in the future. Maybe a year from now. For now let's keep the complexity low. [Edit 3/15/14: Ouch, did I really write this? No, running the broccoli middleware in production will never be good security practice.]

from broccoli.