When using for example shipit for deployment, it deploys into a releases/DATETIME dir and generates a symlink at current; When forever-service is executed in the currentdir, cwd is expaned into the releases/DATETIME and thus having the realpath encoded in the init script, resulting in having to delete and regenerate the scripts for each deployment.
Might be possible to change process.cwd into process.env.PWD though it's possibly platform dependent.
When using for example shipit for deployment, it deploys into a
releases/DATETIMEdir and generates a symlink atcurrent; Whenforever-serviceis executed in thecurrentdir,cwdis expaned into thereleases/DATETIMEand thus having the realpath encoded in the init script, resulting in having to delete and regenerate the scripts for each deployment.Might be possible to change
process.cwdintoprocess.env.PWDthough it's possibly platform dependent.