No luck adding to Gemfile, but it looks like it’s referenced in bower.json. Are there now new requirements not mentioned in the installation instructions?

EDIT: Latest install included in the repo (but not on the wiki here), in doc/INSTALL.md, adds Node.js, npm/bower prerequisites.

EDIT #2 (sorry, I should just take the time to research fully before replying): BUT the release and stable branches refer back to the wiki here for installation [[Installation_OpenProject_3_0]] which makes no reference to those prerequisites. Is this an oversight?

How can i correct it? I don’t know ruby,gems and rails very good. It is important for me because i must make presentation OpenProject to my team and boss for few days. It isn’t possible without right installation.

thanks for the hints. My Setup is on openSuse/MySQL and beta worked perfect for me.
But allthough I tested the other installation instructions (Debian etc.), no success.

Actually I have no time to solve such time consuming installation issues, because we are evaluating OpenProject for our purposes (we aim tight intgegration of eclipse to OpenProject). I have thought, that a simple update to stable release would be as easy as making a coffee (;-)
I’m looking forward to changes of installation docs.

please excuse the late reply! Regarding the problems you seem to have: Bower (a package manager for JavaScript dependencies) was just added to the dev branch. If you like to run the dev (which we don’t recommend for production because a stable is available now) please follow the instructions in the installation manual.

The bower dependency will be mentioned in the HOWTOs as soon as bower becomes part of the stable branch.

I’d recommend to use the stable branch if you want a production system.
However, if you want to test the latest (and greatest) new features of OpenProject, you may use our development branch with Hagens’ instructions.

I’ve just validated my old opinion about Bower on this year Brazilian RubyConf, that have happened last week, which is: Don’t use it with Rails. Simple as that. There are many philosophical reasons not to do so, and the most important one is that you now have 2 different package control system that don’t talk to each other.

A most simplistic solution that works “most of time” (on the edge cases we can just make our own RubyGem or use the existing ones), is to use Rails Assets project.
If you don’t know it yet please take a look: https://rails-assets.org/

It solves the problem by converting bower packages to rubygems and exposing a “rubygems source” address.
You can save everybody from the burden of installing node, then stalling bower, than updating the assets etc…

I know this is not unanimous yet, but I believe that this is the right direction.
(I’ve made this statement with the best of intentions, not trying to bash anyone).