Closed WhiteFire-Sondergaard closed 9 years ago
Hi @WhiteFire-Sondergaard , Hobo runs the "rails" command while creating a new app. To make it work, you can:
rails -v
the result is "4.0.8".Please say if you encounter more issues. Support for Rails 4.1 will come soon!
There's a weakly documented argument for "rails" to force a specific version.
"rails 4.0.8 new thing"
should generate a rails app based on an (installed) 4.0.8.
Could Hobo have a mechanism to pass that through? e.g.
"hobo 4.0.8 new thing"
I've recently been wondering whether this project should be signed up on Travis and have a bunch of different rubies, and rails version automatically checked and reported, so that devs can know what's safe? That'd have to be up to the maintainers, of course. And there may be other priorities - like Rails 4.1 compatibility. :)
Cheers, JeremyC.
On Thu, Jul 31, 2014 at 8:04 AM, Ignacio Huerta notifications@github.com wrote:
Hi @WhiteFire-Sondergaard https://github.com/WhiteFire-Sondergaard , Hobo runs the "rails" command while creating a new app. To make it work, you can:
- Remove Rails 4.1 and ensure you only have Rails 4.0, so when running rails -v the result is "4.0.8".
- Reinstall Rails 4.0 so the "active" binary is "4.0.8"
Please say if you encounter more issues. Support for Rails 4.1 will come soon!
— Reply to this email directly or view it on GitHub https://github.com/Hobo/hobo/issues/97#issuecomment-50722123.
Jeremy Chatfield - Skype: jezchatfield, Mobile: +44(0)7780 607613
Actually why not just have Hobo pass that argument for you? It seems to know what version of rails it's compatible with.
Wow, I didn't know that you could pass the version to the rails command. I'll test it when I come back home, that would be a very nice solution!
Any word on if it works for Hobo?
Hi everyone, I finally had time to work on this. It turns out that the _4.0.9_
syntax works for any gem binary. For example you can use it when you have several Hobo versions: hobo _2.0.1_ new someapp
Knowing this I have prepared a very simple solution for this issue. I have made a commit to master (https://github.com/Hobo/hobo/commit/29ae0f41cb56b82d9539f38cc95d6f784e572d0e) that will allow you to do this:
RAILS_VERSION=4.0.9 hobo new mysuperapp
If you agree this is a nice solution, we can mark this issue as closed, and ready to publish with the next release.
Oh cool. I didn't know that. Any gem, eh?
Looks like a workable method. Needs some documentation, of course.
Thanks, JeremyC
On Thu, Aug 28, 2014 at 4:01 PM, Ignacio Huerta notifications@github.com wrote:
Hi everyone, I finally had time to work on this. It turns out that the 4.0.9 syntax works for any gem binary. For example you can use it when you have several Hobo versions: hobo 2.0.1 new someapp
Knowing this I have prepared a very simple solution for this issue. I have made a commit to master (29ae0f4 https://github.com/Hobo/hobo/commit/29ae0f41cb56b82d9539f38cc95d6f784e572d0e) that will allow you to do this:
RAILS_VERSION=4.0.9 hobo new mysuperapp
If you agree this is a nice solution, we can mark this issue as closed, and ready to publish with the next release.
— Reply to this email directly or view it on GitHub https://github.com/Hobo/hobo/issues/97#issuecomment-53732535.
Jeremy Chatfield - Skype: jezchatfield, Mobile: +44(0)7780 607613
Now we are compatible with Rails 4.2! I think this is solved for now, please write if you encounter issues.
While attempting to create an app
I realize that hobo is not rails 4.1.1 compatible, but the problem is, it's trying to load 4.1.1 parts if they are installed (say, for another rails application.)
This makes it impossible to build a hobo app at all.