I'd suggest debugging that this isn't some weird issue with NPM by doing the following:
within release_path + '/foo/bar' do puts capture(:pwd) Beyond that beware perhaps that `release_path` isn't safe for use at some points in the release workflow, but I can't tell you off the top of my head exactly where. It should be safe to use after/in `deploy:updating`. See http://capistranorb.com/documentation/getting-started/flow/ Lee Hambley http://lee.hambley.name/ +49 (0) 170 298 5667 On 9 March 2015 at 17:49, Chiel Kunkels <ch...@kunkels.me> wrote: > I'm trying to execute npm install in a subdirectory before the release is > symlinked, because composer installs a package which requires it. > > However, when I try > > within release_path + '/foo/bar' do > execute :npm, 'install' > > It can't install, cause it only sees /foo/bar as the path... am I missing > something? > > -- > You received this message because you are subscribed to the Google Groups > "Capistrano" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to capistrano+unsubscr...@googlegroups.com. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/capistrano/b9dfc621-108f-4492-91b5-8202c92e432a%40googlegroups.com > <https://groups.google.com/d/msgid/capistrano/b9dfc621-108f-4492-91b5-8202c92e432a%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group and stop receiving emails from it, send an email to capistrano+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/CAN_%2BVLV2bEfM4EWVcLFtPBH0cqf2z5xUFEWXErh-mkiy6U9ahA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
