Skip to content

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

@fantapop

Description

@fantapop

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'

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions