-
-
Save brookr/2493622 to your computer and use it in GitHub Desktop.
# From the project root | |
rvm env -- `rvm current` >> .powenv |
At the very least, pow should detect the .ruby-gemset file and issue a warning like it does for a detected .rvmrc file...
Thanks for the script @denro, but it's unfortunate that it's still necessary today.
so pow dont use the ruby-gemset YET?
@jetsgit, do you still need to configure a .powrc
to accept the .ruby-gemset
and .ruby-version
files correctly? Like in this gist: https://gist.github.com/nbibler/5307941 ?
@kWhittington, ---I discovered the solution @denro mentioned is still necessary and still works great.
If you wish to debug using POW and pry-remote, you can do the following:
echo 3000 > ~/.pow/yourapp
However, that will cause an annoying error, e.g.:
/Users/jet/.rvm/hooks/after_use_update_powrc:6: parse error: condition expected: /Users/jet/Rails_Projects/puget-sound-salmon
To fix that, modify the bash script to the following, which will only exec on symlinks:
# ~/.rvm/hooks/after_use_update_powrc
for file in `ls ~/.pow/` ; do
POW_LINK_TARGET=`readlink ~/.pow/$file`
if [ -L "$POW_LINK_TARGET" ]; then
if [ `pwd` = $POW_LINK_TARGET ]; then
rvm env -- ``rvm current`` > .powenv
fi
fi
done
is there even simpler way? will the next pow release support .ruby-gemset?