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

How to get forever working with locomotive #166

Open
rapsody opened this issue Feb 8, 2015 · 4 comments
Open

How to get forever working with locomotive #166

rapsody opened this issue Feb 8, 2015 · 4 comments

Comments

@rapsody
Copy link

rapsody commented Feb 8, 2015

Hi, using the command forever start -c 'lcm server' with locomotive v0.4 and the command doesn't work. Is it possible to have forever work with locomotive

@crispen-smith
Copy link

While I can't speak to this in any "official" capacity, I can say that I've got forever working for my install.

Two things 1) I have a global install, just for a fallback (i.e. npm install -g locomotive)
2) I also have a local install as part of my application package.

My structure looks basically like:
working dir/
site/
app/
config/
node_modules/

as long as I am in Site/ I can run: forever node_modules/.bin/lcm server and get good results.

I seem to recall trying it one level up as forever site/node_modules/.bin/lcm server and having issue so I believe there is some patch magic inside locomotive that requires you to run it from the parent of app/

@rapsody
Copy link
Author

rapsody commented Feb 9, 2015

Thanks for the reply, this works. its a little weird that its doesn't work as a global command, ie havng to be in site dir to run, but hey you can't win them all.

Thats a similar structure to what i have already, so all good.

@crispen-smith
Copy link

Good news then. :)

@OtaK
Copy link

OtaK commented Sep 10, 2015

Well, I'm simply doing NODE_ENV=[env] forever start server.js. Works great.

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

3 participants