Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 4 years ago.
Improve this question
Production, and development work just fine, but the test environment doesn't want to migrate.
Does anyone have any idea as to why the gem is not working for the migration?
Did you run bundle exec rspec:install ?
In case you have multiple versions of rspec, you can try bundle exec rspec so it calls the one defined in your Gemfile.
Instead of require, try require_relative, that way, the path is resolved regardless of the location from which you're calling the script.
I ended up removing the repo, and deleting my database then re-installing everything which seemed to do the trick.
Related
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 3 years ago.
Improve this question
I am a beginner just starting to learn ruby. The tutorials I have been reading say that I can create a file with the extension .rb(eg. hello.rb) and run the file in the command prompt by typing ruby hello.rb. But when I create and save the file on the desktop and run it in the cmd it always gives me this error message:
C:\Windows\system32>ruby hello.rb
Traceback (most recent call last):
ruby: No such file or directory -- hello.rb (LoadError)
I searched the internet and read a lot of other tutorials but none of them seem to have any discussion on this issue.
Can someone give me any hints on this please?
Any advice or help will be greatly appreciated!
You should provide the correct path to your file, since it's not located in system32 directory, this relative path won't work. If it's on the desktop, it would be something like this, probably:
ruby %HOMEPATH%\Desktop\hello.rb
or you can change your current directory to desktop before you start playing with ruby:
cd %HOMEPATH%\Desktop
from now on, you can easily use relative path, since hello.rb is located in the same directory you're in currently in your command line:
ruby hello.rb
I'm not quite sure of exact syntax etc, I don't use Windows cmd very often - you would have to experiment on your own.
There may be context menu option like "open command line here" in Windows, but I'm not sure of it as well.
Also, you may need to learn basics of command line even before you start to learn Ruby.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 7 years ago.
Improve this question
I have built a basic CRM app to learn Ember. The app uses a Rails back end; and Ember and Rails communicate with a JSON api. Feel free to check out the source code on my GitHub. The app is hosted here.
The app works great in my development environment, and deploys to Heroku with no issues whatsoever.
However, when I navigate to the apps URL I see a blank page. Further inspection using Chrome's dev tools tells me that none of my javascript files were sent from Heroku to my browser. What gives?
The solution was to add the rails_12factor gem to my Gemfile. It looks like for any Rails/Ember app to work correctly on Heroku, this gem is required.
As per Heroku:
Heroku integration has previously relied on using the Rails plugin
system, which has been removed from Rails 4. To enable features such
as static asset serving and logging on Heroku please add
rails_12factor gem to your Gemfile.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 9 years ago.
Improve this question
https://github.com/justuseapen/omrails
Link to the repo^
When I run the app on my local server I get a syntax error in the browser. Apparently something wrong with the <%= end %> in my application.html.erb file.
I followed the onemonthrails tut as exactly as possible, excluding the heroku pushes because I cannot for the life of me get my ssh keys to line up (that's for another question).
Also, when I run rake db:migrate (or bundle exec db.migrate) I get an error that says
don't know how to build task db.migrate
Any suggestions on a fix? I already check this question: Don't know how to build task 'db:migrate' w/ Rails 3.2.0.rc2
and found no relevant solution but perhaps I'm missing something.
Without knowing more specifics, it might be that <%= end %> should be written as <% end %> (no =) is the trouble with your application.html.erb
Also, bundle exec db.migrate should be bundle exec db:migrate (: rather than .)
I am often pointed to the source of typo blog engine i.e., http://typosphere.org/stable.tar.gz But, if I download and perform the following: bundle install etc. it runs as a separate engine.
I tried installing typo as a gem, I tried the following:
gem install typo
typo install /some/path this fails, saying 'Typo command not found'
How to integrate typo blog engine with existing app, any pointers would be welcome.
Typo is a Rails project. I am happy to say that I contributed to it at one point of time.
You asked in comments, that you wish to use database of Typo in your main application. For that, I'll suggest you to check out connection_ninja.
However, there are many gotchas with these type of configurations.
Good luck.
PS: Just noticed that this question was asked long ago. Ouch!
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
How to remove unit test and replace it with rspec?
Kinda odd question here: when you go with rpsec instead of test::unit on rails, what do you do with the test dir? Keep it (for any compatibility issues maybe?) or remove it?
I have always kept it, in case some plugin or generator expects to find it there.
If you don't like having the test directory, I suggest you try to remove it and see if it works. You can always recreate it later, if you notice that you need it.