I want to upgrade from 1.0.1 to 3.1.1
what are the steps? and what is prerequists to install 3.1.1?
what is ruby version and gem is compatible with 3.1.1 ?
thnx in advanced
Redmine 3 runs Rails 4 so it's prerequisites apply. You should at least run Ruby 2.0.
Redmine itself is easily upgraded,
everything else depends on which plugins you are running if any, and if these are still maintained and available in a version compatible with Redmine 3.1.
Related
I have just installed URU in order to manage different ruby installs. I am actually upgrading from Ruby 2.16 to 2.26 in order to upgrade my Rails app from Rails 4 to Rails 5.
I have not yet decided to upgrade to Rails 5 but instead using the new ruby version (2.26) to go on developping my current app.
Though when trying to do a rake db:migrate I ended up with a no such file error while reverting to ruby 2.16 the rake db:migrate went successfully.
I have installed this new version with Ruby installer for Windows, skipping the Devkit as it should be the same a for the 2.16 version.
Any idea where the problem comes from ?
I have manually Upgraded Susy 2.2.3 to 2.2.6. Can I delete older version or will it automatically uses latest version. I have Ruby Compass Sass and Susy Brianran
Sass should automatically use the latest version, but you can also delete the old one. gem cleanup susy will do that for you, assuming Susy is installed as a ruby gem.
I run rails generate controller welcome index
I got the warning
You're using Rubygems 2.0.14 with Spring. Upgrade to at least Rubygems 2.1.0 and run gem pristine --all
I updated gem --system and also added paths into ~/.bashrc, but still same result, is there any suggestion?
Since I had an older Ruby version 2.0 from the past, so it made apache confuse. I could either explicitly telling apache to use which directory, or use RVM (Ruby Version Manager) which do all jobs. Just need to go through these steps:
Install RVM:
rvm get stable --auto-dotfiles
Then tell which version you tend to use:
rvm use 2.2.0
Update gems
gem install rails
Now ready to go!
Go to your Gemfile.lock and change your version of Ruby. That might do it.
What Ruby manager are you using?
im a noob. i need help.
im trying to install Redmine CRM plugin however im getting an error when i run this:
bundle install --without development test
it says:
Bundler could not find compatible versions for gem "i18n":
In Gemfile:
rails (= 4.2.0) ruby depends on
railties (= 4.2.0) ruby depends on
activesupport (= 4.2.0) ruby depends on
i18n (~> 0.7) ruby
money (~> 5.1.0) ruby depends on
i18n (~> 0.6.0) ruby
Redmine CRM plugin has to be upgraded to newer versions of redmine in parallel. I recommend to upgrade redmine first (with an empty plugins directory) and then add the redminecrm plugins and upgrade them too.
Redmine CRM Plugin 4.0.3 is compatible with Redmine 2.6-3.1
Older versions of the Redmine CRM Plugin installed on Redmine 3.1 result in the error you posted.
In your Gemfile, manually specify I18n gem like
gem 'I18n', '~0.6.0'
I'm starting to experiment with Rails 4 for work where we are using the MySQL2 3.1.0 gem on the server.
Locally with Ruby 2.0, I installed the MySQL2 3.1.0 Gem and everything was fine there (matching the gem version on the work server basically just to match the production server environment).
When I created a new Application (ruby new r4_test -d mysql) I ran into a problem though. Bundler crashed during the new application creation process complaining about missing MySQL2 3.1.3 files. It looks like 3.1.3 (released 3 months ago if I'm looking right) is the highest version number of the MySQL2 Gem. I'm confused about this because the only version of MySQL2 installed in the Ruby folder is version 3.1.0. Why did Bundler ignore the installed gem and expect a higher version that wasn't installed locally? I skipped Rails3 so I'm new to Bundler. It doesn't seem like it should expect a version that's not local though. Sometimes there are bugs or other issues where you need to stay on an older version of a gem for awhile too. ?
Thanks!
If you don't already have a Gemfile.lock in your project directory, Bundler tries to install the most recent version available that meets the version criteria in Gemfile. So, for a new Rails project, it will try to install the latest dependencies of the default generated Gemfile. It doesn't actually look at your installed gems at all unless you already have a Gemfile.lock.
You can use the --skip-bundle (or -B) if you don't want Rails to run bundle install when creating a new project. That gives you a chance to customize the Gemfile first. You can add in a version constraint if you want to be sure it will use the version you already have installed.