Build create directory dist/public but when start expect dist/client

[gintsgints]

When I build generated package with grunt build, it makes dist directory and client side files in directory public.
But when I strart dist/server/app.js, it expect files to be in directory - client.

[JaKXz]

Are you using/have you tried grunt serve:dist? If you're just running the server from node directly you need to set your NODE_ENV to production.

[gintsgints]

Why grunt serve? I do not deliver grunt with built package :)

Should I set NODE_ENV for build or for start (I start my project with node dist/server/app.js?

[kobkrit]

You should run
$ cd dist
$ NODE_ENV=production node server/app.js

Yours faithfully,

Dr. Kobkrit Viriyayudhakorn
CEO
Connector Company Limited

On Thu, Jul 24, 2014 at 3:28 PM, Gints notifications@github.com wrote:

Why grunt serve? I do not deliver grunt with build package :)

Should I set NODE_ENV for build or for start (I start my project with node
dist/server/app.js?

—
Reply to this email directly or view it on GitHub
#387 (comment)
.

[gintsgints]

For me does not sound good. That to start production server I have to setup enviroment variable.

[gintsgints]

Same problem when I clone project from git and just do npm install, bower install, grunt test, grunt serve

[JaKXz]

@gintsgints again, if you want to be testing in the production environment, you need to run the grunt serve:dist task. Or, as was suggested, you need to set the Node environment to production.

[gintsgints]

So when I need to start work (not test production) from new git repo, it is meant so I have to set up enviroment variable?

[aaroninaustin]

I found this comment while searching for my own issue and thought it might be worth a quick follow up from someone else who uses this really excellent framework/generator... Hope it helps.

Whenever you start a new project or clone an existing project to a new environment for development - this could be your laptop or a test server, you will want to run grunt, bower and npm, etc.

This includes lots of code from other sources you don't want to track in your own repository. Only when you are ready to deploy code to a production server will you need to use the grunt build command, set the NODE_ENV environment variable and copy over the /dist folder.

Two reasons for this in production:
This will disable the verbose logging you use in the development environment
This will eliminate the need to have all of the development tools, like grunt and bower, you need on your testing servers and local machines.

Setting the NODE_ENV is kind of a pain, but its pretty standard practice and keeps your code cleaner as you won't need to change anything in the code that is pushed to production to let the framework know its time to run in production mode.

Hope this helped,