-
Website
http://www.chrisdpratt.com -
Original page
http://www.chrisdpratt.com/2007/09/17/ruby-on-rails-development-in-windows-via-cygwin/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
Shane Sponagle
1 comment · 3 points
-
Chris Pratt
21 comments · 1 points
-
ibrahimahmed
1 comment · 1 points
-
robbykeller
1 comment · 1 points
-
besman
1 comment · 1 points
-
-
Popular Threads
I've made it harder for myself by using sqlite3 rather than mysql, which is complaining about a segmentation fault. It's going to be a long night!
Now it's all working, but I find autotest running incredibly slowly? Do you have the same problem, or any fixes for it?
However, I am experiencing the same slowdown, so it's only a matter of time before I finally get fed up enough to thoroughly investigate the matter. If you come across something first, though, send it my way.
I use a mac at home but unfortunately have to use Windows XP at work. I stumbled across this when I was trying to recreate my nice mac development environment on Windows.
I use cygwin and e-text-editor and I tried hard to get rspec working with autotest and snarl. I have come to rest at the solution you provide above - without snarl but hey coloured autotests.
However, when using edge rails, I have found the above does not work - do you have a similar experience?
I just tried to install the RSpec plugins on an edge rails and everything was fine until I tried to generate the default RSpec files and folders (ruby script/generate rspec)... It errors out every time. I even tried the trunk version or RSpec in addition to the current release, with the same results.
Just to be thorough, I tried generating rspec before freezing edge, but whatever the issue is seems to affect all rspec generators, as I couldn't get the rspec_model or rspec_controller generators to work in edge either. Now, it's possible to manually create your specs without the generators, so I went ahead and tried autotest on some existing specs, which failed as well.
It would appear that RSpec is completely broken in Edge Rails, at least on Windows. However, if I had to guess, I would say its actually that edge rails runs from the plugin directory that is giving RSpec problems, rather than some new change in Rails itself.
I might end up adding this tracker, but I'm hesitant since it's asking for a change to support something that is itself experimental in nature. Actually, more likely than not, I'll simply mention it on the RSpec mailing list, and see what people come up with.
Thanks for noticing this.
> rake db:drop:all
I get the following error:
> "This task only drops local databases. mp is on a remote host."
> rake aborted!
It seems that by setting my database to 127.0.0.1, rake can't modify my database.
Has anyone else run into this?
I ran into the same problem. Setting your database to localhost fixes the problem and as far as I know, there's no difference between the two.
*thinks*
Unless there is, and I just broke something vital. Oh well.