Forever changes current working directory when script path is absolute

[boutell]

If I use:

forever start /opt/stagecoach/apps/example/deployments/2012-04-23-09-46-19/server.js

The current working directory is changed to / by forever before the script is run (verified with process.cwd()).

If I use:

forever start server.js

I do not see this problem, the current working directory is left alone.

I am not sure if the --sourceDir option is meant to help with this, but it does not appear to.

Thanks for an excellent process babysitter!

[bryankaplan]

I can reproduce this.

[hrishikeshio]

I am having trouble with --sourceDir also... It does not seem to work..

[indexzero]

This should be fixed. There are tests that confirm this works.

[tommedema]

Why was this closed?

[joelweinberger]

Just to add my 2 cents, I just started experiencing this problem. Perhaps it has regressed?

[julianduque]

I'll investigate, will reopen

[jossscholten]

Also seeing this issue. When forever is run from a script that references an absolute path, process.cwd() returns the script directory instead of the local directory.

[luiselizondo]

An easy way to reproduce the problem is to use the express-config module (https://github.com/blahed/express-config) and then run forever from any directory except the one with the application

[christiangenco]

+1

[osher]

+1

• we got the same problem - forever version - 0.10.11 with node version 0.10.24

currenlty we patch it with performing cd always before running forever

[pkopac]

0.11.0 worked well, but 0.11.1 broke it again; solved by fixing version on 0.11.0

[tommedema]

is forever still maintained? any alternatives?

[jrowny]

+1