Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

running in production mode fails if assets directory doesn't exist #7

Open
fantapop opened this issue Apr 25, 2014 · 0 comments
Open

Comments

@fantapop
Copy link

The co-assets-compiler used in production mode seems to require the asset directory to exist before starting up the server.

I get the following error when it doesn't exist:

$ NODE_ENV=production node .
connect.multipart() will be removed in connect 3.0
visit https://github.com/senchalabs/connect/wiki/Connect-3.0 for alternatives
connect.limit() will be removed in connect 3.0
AssetsCompiler Precompiling assets: coffee, styl
Hatch server listening on premium:3000 within production environment
uncaughtException
uncaughtException: ENOENT, readdir '/home/chrisf/dev/hatchjs/app/assets'
Notify error
uncaughtException: ENOENT, readdir '/home/chrisf/dev/hatchjs/app/assets'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant