-
Notifications
You must be signed in to change notification settings - Fork 258
Pow ignoring rvm #271
Comments
I would like to confirm that I am having the same problem I read in this issue. I just updated my RVM to 1.11.3 and all of my sites using Pow are broken. I can start them without Pow. I have followed the troubleshooting tips to no avail. All I see when I go to my apps is: Error starting application |
One of the RVM guys (@mpapis) just helped me solve this issue. He had me comment out line #9 of my Users/myname/.rvm/scripts/rvm file. He concluded this is a POW issue and that I would need to repeat the fix each time I updated RVM.
|
the issue is that POW tries to load RVM in an limited shell - SH, this was never supported by RVM, but we had to disable it explicitly because of problems in starting X server in Fedora 16 RVM supports Bash and Zsh, any other shells are not tested neither supposed to work (SH is not supported). |
After disabling this line I do indeed get it back up but then when I reload pow I get Application not found for all aps The fix is to unpatch RVM load pow then patch RVM. This is not a great solution for me. Are you getting any problems if you restart pow? |
Latest bleeding edge POW still needs the fix but now doesnt lose my Apps once it runs |
same issue here |
i have the same issue...... @simontseng May I know how to downgrade? I searched the web and can't find any resource. |
http://beginrescueend.com/rvm/install/ read "Installing a specific version:" |
ooops. Thanks @simontseng :) |
@Aesthetica thanks! 👍 |
Works for me: bash -s -- --version 1.10.3 < <(curl -s https://raw.github.com/wayneeseguin/rvm/master/binscripts/rvm-installer ) |
Equals to
|
Downgrading to 1.10.3 worked for me too. |
Fixed problems I was having as well. |
does anyone know if this issue going to be resolved? is it solved in edge version of pow? or should this be an rvm issue? i guess not updating rvm forever should be the solution |
From what I understood RVM support might get dropped anyway: #236 According to http://pow.cx/manual you should be able to source proper environment file from
I do not use pow so I did not had chance to test it, but it should work after |
that would be quite disappointing actually. Pow is supposed to make it dead easy to get rails apps up and running on a dev machine, no? |
according to the docs - http://pow.cx/manual it would require you to type for every changes in code or do it once: In the end finally pow is available only on osx, if you do some work with linux (like via vagrant) then you need to learn back to standard ways. |
didn't know this is because pow is moving away from rvm |
the .powrc solution does make sense |
dropping rvm support does make sense to me |
::watching:: |
I've had luck dumping the rvm environment into the .powenv file from the .rvmrc:
This way POW will be automatically configured for your local environment as RVM is being configured. I've tested this workaround with success on RVMs 1.11.x and 1.12.x using POW 0.4.0 |
@thatothermitch's solution works for me w/ rvm v1.12.3 and Pow v0.4.0-pre |
@thatothermitch's solution worked for me, too. rvm 1.12.4 and Pow v0.3.2. |
@thatothermitch's solution worked on rvm 1.12.5 and pow v0.3.2. Can the docs be updated with |
Just hit this. Also a co-worker hit this a week ago and switched to +1 |
rvm and pow singing -- Why can't we be friends !!! |
@thatothermitch's solution worked for me, too. |
Summary:
|
I'd like to note that the solution of @thatothermitch didn't work with my ZSH shell:
But it works when running it in bash:
|
@alexschomb at the risk of insulting you (sorry if that's the case) you need to use a real version of ruby and a real gemset name... so if your app's gemset was 'my_cool_app' and you wanted to use Ruby 1.9.3 patch level 125 then it'd be:
Worked a treat for my zsh |
@J2Fly No worries, you can't insult me that way ;) At first I thought the same, but on my zsh it didn't even work when replacing it with real versions and gemsets. I'm quite unsure what I did wrong here. Although it works like a charm in bash even without replacing the |
You know you might be right, it might pick out the version of ruby and the gemset for you based on your current rvm env settings. Running it with explicit versions when I tried it fixed me right up though so I can't speak to whether or not that is how it's supposed to work. |
Fixed in 584a40d. For the record, this kind of bug—stemming from poorly-defined or nonexistent APIs between RVM and the rest of the world—is exactly why I wrote rbenv, and why we'll be dropping automatic RVM support in a future Pow release. |
For the record, Pow hadn't been updated in like 9 months. RVM is regularly updated and it's creators are very helpful. Non-existent APIs vs. non-existent updates. Hmmm... buh-bye Pow. |
@Aesthetica Open-source software is provided free of charge for you to do with as you please. Use it or don't. No one owes you anything. |
I am fully aware and appreciate that open-source software is free and realize that I couldn't code a replacement for Pow or RVM much less build a gem. I just think your comment stepping on RVM seems heavy handed. |
Fixes basecamp#271, basecamp#281, basecamp#285, and probably other rvm-related issues.
What if I'm getting this issue while using rbenv ? :( |
@haggen - from the Pow user manual:
Here's the full entry: http://pow.cx/manual.html#section_2.3.1 Hope that helps; I'd offer some specific tips, but I'm more of an RVM guy myself, sorry! |
Ok just to say I have spent 4 days looking for fixes so I realise this has been looked at before and closed
I am getting the
I have tried a reinstall of everything including different version of ruby and rvm. everything is now on latest versions
I have also added the RVM botoing to .zshenv and hardcoded the path
I have downloaded and installed from source the latest head of pow and get the following output from the new (and very useful) /env.json
I have also tried rackup in the project directory and it runs fine
I am having the same problem across all of our apps as well
Any suggestion sother than "have you tried rbenv" are welcomed
The text was updated successfully, but these errors were encountered: