5

I know there is an entry on the Troubleshooting wiki page for Pow, but I made that change and it still gives the same error.

If you notice from the error message below, it seems to be at least trying to use the correct version of ruby from rbenv, but still has the same error

LoadError: cannot load such file -- bundler/setup
~/.rbenv/versions/1.9.3-p125/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
~/.rbenv/versions/1.9.3-p125/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'

I also looked through all the comments in the issue mentioned on the troubleshooting page as well and none of those solutions work for me.

Bernhard Barker
  • 54,589
  • 14
  • 104
  • 138
camdub
  • 867
  • 1
  • 10
  • 22

6 Answers6

5

Generally, you need a ~/.powconfig file with:

export PATH=$(rbenv root)/shims:$(rbenv root)/bin:$PATH

See the issue discussion and the pow guide.

New Alexandria
  • 6,951
  • 4
  • 57
  • 77
  • 1
    A like to use a slight variation on this in order to avoid hardcoding the `.rbenv` path: `export PATH=$(rbenv root)/shims:$(rbenv root)/bin:$PATH` – markquezada Nov 20 '14 at 00:44
  • Thanks, this is definitely a more robust pattern that I have seen since the time I wrote this answer. updated – New Alexandria Nov 20 '14 at 21:45
2

1) cat ~/.powconfig

export PATH=/Users/alvin/.rbenv/shims:$PATH

2) restart

touch ~/.pow/restart.txt

alvin2ye
  • 147
  • 2
  • 4
1

I had this error using rbenv and simply uninstalling and re-installing pow fixed it:

curl get.pow.cx/uninstall.sh | sh

and

curl get.pow.cx | sh

David DeGraw
  • 11
  • 1
0

I figured it out. For some reason I have two .rbenv shims directories. One in ~/.rbenv/shims and one in ~/Developer/.rbenv/shims.

By changing my ~/.powconfig to add the Developer directories to my path, pow ran the app fine.

camdub
  • 867
  • 1
  • 10
  • 22
0

Just for completeness.

I was having a similar issue and the answer over here fixed it for me.

I had to remove ~/.ruby-version in order for it to work for me.

Community
  • 1
  • 1
RyanJM
  • 7,028
  • 8
  • 60
  • 90
0

I'm using rbenv, and had this problem, when as suggested by this answer, the version of Ruby was different in the app's ENV than it was for Pow.

I had set the Ruby version using the RBENV_VERSION environment variable, which for some reason was not picked up by Pow. This was fixed by creating a .ruby-version file in the directory of my project.

Community
  • 1
  • 1
Derek Hill
  • 5,965
  • 5
  • 55
  • 74