Tag Info

Hot answers tagged

126

Try adding -V (upper case) to the end of the install command, if forces the command to be verbose, so you can see things going on. Eg: sudo gem install rails -V


48

It'll take quite some time to install rails - there are lot of dependencies and these need to be downloaded - if you have a slow connection, just wait for a bit.


19

Method 1 – railsready If you don't want to do everything manually, you can use the railsready script, which will install for you: An updated system (Linux only) Ruby 1.9.3 latest patch level (installed to /usr/local/bin/ruby) or RVM running 1.9.3 latest patch level Imagemagick libs needed to run Rails (sqlite, mysql, etc) Bundler, Passenger, ...


7

From: Don’t be terrified of building native extensions! - Pat Shaughnessy The native extension is some C code that’s included inside the Ruby gem that calls the external component’s API, converting the parameters and return values between the format the external library needs and what the Ruby interpreter expects. The Xcode installer package contains ...


6

The problem will be that you didn't start Apache as root - by default on any unix based operating system only root can bind a process to a port below 1024. Your choices are to either use a port higher than 1023 and remember to specify it when you connect, or to ensure that you start Apache as root. Unfortunately not being a Mac user I can't provide details ...


6

You should use apt-get If you care about uninstalling gems with their dependencies. RubyGems will not uninstall unused dependencies. See do-i-have-to-manually-uninstall-all-dependent-gems. If you care about uninstalling gems as a group, rvm is also an option (see below). If that gem would or should install executables in /usr/bin. If you want to upgrade ...


5

Try using Homebrew and/or RVM RVM allows you tO have several versions of ruby installed if you want. Homebrew is a nice package manager for Os X.


4

Does this help? Go to my System Preferences.app and open “Sharing” pane. Disabling the Web-Sharing service. Launch Terminal.app and stopping httpd (apache) with the following command: sudo apachectl -k stop Going into the Activity Monitor.app and searching for “httpd”. Select both processes and click on “Stop”. Shutdown and start ...


4

Personally, I gave up on getting 1.9.2 running with Rails 3 & Heroku for the time being. However OSDIR mailing list mentions below instructions $ rvm remove 1.9.2 $ rvm package install openssl $ rvm install 1.9.2 -C --with-openssl-dir=$HOME/.rvm/usr


4

Install Ruby Version Manager! Seriously! I wish I would have done this sooner. Ruby Version Manager makes it possible to run multiple versions of Ruby, each with their own set of gems, and switch between the different versions seemlessly. Plus, you won't have to use sudo anymore. Plus, it's super easy to install, so you should do it!


4

You should always use RubyGems to install any kind of Gems (eg. Rails) to reduce confusion. Ruby on Rails: gem install versus apt-get


4

As mentioned in my comment, first make sure that both ruby and gem point to the RVM-installed versions, and not the ones in /usr/bin. Also make sure you use your new Ruby as default: rvm --default use 2.0.0-p247 Create a Gemset (called gemset) that will be used for this Ruby version: rvm use 2.0.0-p247@gemset --create --default Then install Rails to ...


3

I struggled with that as well. Just use: vagrant plugin install any-plugin


3

What to do with a Ruby git repo depends on what is in it, and usually described how to use it by the README. In this case, the repo is for a gem, and it does not contain any Rails server examples or Rails projects. Unless you have a specific need to use the github version, you should just use the version from rubygems.org Ignore your cloned item for now, ...


3

Looks like the rvm installer is trying to run apt-get to install missing dependencies, we can fix that by pre installing them. Try running this as root: sudo apt-get install curl bison build-essential zlib1g-dev libssl-dev libreadline5-dev libxml2-dev git-core And now try running your install command again as the Jenkins user.


3

This is how you do it, tar cfz target.tgz --directory=TARGET_DIR subdir_list In your case it would look like, tar cfz target.tgz --directory=app/c3ec2057-7d3a-40d9-9a9d-d5c3fe3ffd6f/home/tmp export/


3

Updated to the latest version of rvm rvm get stable and then ran rvm reload rvm reload which seems to have solved this issue.


3

Your ruby version is fine, 1.9 is still a little experimental and there are a number of libraries that don't work quite right with it yet. You'll also want to upgrade ruby gems itself, and seeing as you have quite an old version you'll want to use these two commands: sudo gem install rubygems-update sudo update_rubygems Which should install ruby gems ...


3

If you are using Passenger, then it's monitoring the timestamp of the tmp/restart.txt file to trigger restarts.


3

Ruby installs on Debian/Ubuntu don't seem to generate the symbolic /usr/bin/ruby link to the specific install you have (theoretically, so that you can have multiple versions installed point to whatever version you want to use as your default). so... sudo ln -s /usr/bin/ruby1.9.1 /usr/bin/ruby should get you rolling. If which ruby1.9.1 is returning a ...


3

This issue has recently been fixed. Run rvm get head and you should be able to set a default gemset and have it persist across Terminal sessions. More info is here: https://github.com/wayneeseguin/rvm/issues/710


3

Have you tried using Tab? gedit myTabviTabuTabshTabhtTab Enter or such depending on how well your folders are named.


3

Remove the .gem folder in your $HOME folder will fix this.


2

The problem wasn't the port 80 thing. Neither the IIS thing thats mentioned usually. Nor helped several reinstalls with different tricks (delete the records in regedit linked to wamp is mentioned usually). The solution was a kind of localhost issue. Steps: Try - http://127.0.0.1 - if it shows up the WAMP start page than you are on the right path Open the ...


2

try running sudo find / -name rails* that will find any files in the file system starting with rails


2

You can find the default location where Gem executables will be installed with: ruby1.9.1 -rubygems -e 'puts Gem.default_bindir' On Debian 6.0, this is /var/lib/gems/1.9.1/bin, so the rails binary is /var/lib/gems/1.9.1/bin/rails. If you use a lot of RubyGems with executables on your system(s), I would add this bin directory to your PATH. export ...


2

You might consider defining a simple shell variable: cd my_app VIEWS=app/viwes/user gedit $VIEWS/show.html.erb gedit $VIEWS/xy.html.erb Chose a shorter variable if you're a really lazy guy.


2

The error message you're receiving is because the new version of Rails requires a newer version of gem than you have. You can update gem like this: gem update --system You may need sudo if you're using system gem. You can check the version of gem by running: gem -v Once this is done, and you can confirm your gem version is at least 1.3.6, you should be ...


2

Two things here: rake db:migrate RAILS_ENV=production really is different from RAILS_ENV=production rake db:migrate as the former one pass the string RAILS_ENV=production as an argument to rake while the latter declares an environnement variable in your shell. You should use export RAILS_ENV=production then run rake db:migrate in the same shell ...


2

First, don't update the built-in Ruby. Apple put it there for their use. If you want to piggy-back on it without changes, that's fine. If you make changes you run the risk of affecting apps that expect it to be at the standard Apple-installation version. Instead, I recommend RVM for installing a separate version of Ruby for your own use. RVM makes it easy ...



Only top voted, non community-wiki answers of a minimum length are eligible