Directory Structure

[sudhakar]

I am wondering the reasoning behind having separate directories for build & compile. In brunch, it creates only _public directory which contains derived files based on which command you use because you would rarely use both development and production at the same time.

Also can karma-unit.tpl.js be moved out of karma subdirectory to toplevel?

If you are ok with it, I can probably raise a PR..

[joshdmiller]

The reason for the separate build and compile directories is that the build contains a lot of temporary files that are needed during the compile. If we were to push all the compiled files into the same directory, it would be difficult for the developer to know which files to deploy to his server. As it exists now, the build directory is just a convenience - it does the bare minimum to keep the app running in a dev cycle; but the compile directory is entirely self-contained and ready for production. So it's true that you wouldn't do development and production at the same time, but one builds on the other; you can't compile without first building.

As for the karma config, I don't really have a preference. It is in a subdirectory right now because I plan to add a separate config for E2E tests and when there are multiple related files, I like to put them in a subdirectory. But if you can rally support behind the idea of putting them in the root, then that would be fine. Whatever the community wants here. :-)

[sudhakar]

@joshdmiller Got it. That explains why we have bin and build directory. In my case, I dont deploy bin to the server, instead I pull from projects git repo, do npm install to update the dependencies.

Yep, it just a matter of taste and I am equally happy with having separate directories as well :)

Cheers for your great work.