Content
Noob trying to change something
Added by Steven Schveighoffer over 9 years ago
I just was trying to install a development copy of openproject so I can play around with adding the feature I talked about here: https://community.openproject.org/topics/4434
I’ve followed these instructions:
https://www.openproject.org/open-source/development/setting-development-environment/
The only thing I’ll note is that ‘bower install’ reports an error that it cannot find ‘bower.json’, in the git root directory.
When I go to the localhost:3000 address, I get this message:
couldn’t find file ‘bundles/openproject-global’
(in /home/steves/openproject/openproject/app/assets/stylesheets/default.css.sass:28)
I have no idea how ruby or rails works. The amount of “packages” downloaded by a multitude of package management software is extremely intimidating! You guys use a lot of external stuff.
I’m just trying to get to a working development installation so I can play with a couple lines of code. Any ideas on what I did wrong?
Replies (5)
You have to run
bower install
from within the “frontend” directory. This should create the missing files.Stefan, Thanks for the help, but I had actually already tried that (did a find command to see if I could find any ‘bower.json’ files). The referenced page I linked above should probably be updated to fix the instructions (it does not say to run inside the frontend directory).
In any case, the result of running
bower install
there is no output, and no change, it still fails :(Just checked out a fresh copy of openproject. I guess sth. has changed with bower or npm.
Running
webpack
within the “frontend” directory creates the missing files. These can then be found inapp/assets/javascripts/bundles
.Worked for me. Can you confirm?
webpack as an application wasn’t found.
running:
And running the resulting binary (./frontend/node_modules/.bin/webpack) seems to have gotten an openproject screen up instead of an error so that is good :) (perhaps there is a more standard way to run that?)
But trying to log in as admin failed. I deleted the whole thing and started over, in case there was something I missed. And… with seeded data, it works!
So here is a list of things I think need work on the “setting up a development environment” page:
npm install
command runs thebower install
from the correct directory. I think this is likely why it didn’t do anything (it had already run on a previous step).openproject_test
) with a big exception.Thank you for all your help! I would never have figured that out :D
If you would like, I can create a bug report for the list above.
Great to read you have your installation running. Please create the bug report. This would be gread. We then update the installation instructions.
The thing with the 200 tabs is most likely because of the letter_opener gem which opens all sent mails in the browser :unamused: