installtion issues
Added by blackbeard . almost 7 years ago
So I have been working on this issue for 5 days now. I have followed the following how to guides;
Install Redmine 3.4.x on Ubuntu 16.04 (rvm + nginx + Phusion Passenger + MySQL)
Install Redmine 3.0.x on Ubuntu 14.04 (Apache2, Phusion Passenger, MySQL, Subversion and Gitolite)
Install Redmine 2.5.x on Ubuntu 14.04 (Apache2, Phusion Passenger, MySQL and Subversion)
and
http://www.untrustedconnection.com/2018/01/redmine-passenger-and-nginx-on-ubuntu.html
As well as any video tutorial I could find, yet I can never get Redmine to install properly.
A couple of months ago, I was easily able to follow the a offical guide and install it flawlessly, but due to some migrations I deleted the old system. I swear I don't remember doing anything with gems, ruby, or rails at the time and it worked. Now I can't get it to install. I have tried using Ubuntu 14.04 and 16.04.
I have a VM set up using hyper-v on Ubuntu 16.04.
I've tried again today on a freshly download ubuntu iso, and new vm. and when I use
bundle exec rake generate_secret_token
I get an error, something about bundle not installed, after googling the hell out of it, nothing works.
There are times when I am close, but apache2 displays the site as index of/
Tomorrow I will try again and then I can provide more specific errors and logs. However is there any resolution?
Replies (4)
RE: installtion issues - Added by blackbeard . almost 7 years ago
So following this http://www.untrustedconnection.com/2018/01/redmine-passenger-and-nginx-on-ubuntu.html guide word for word, does not work. During the Ruby Installation, when I run
rvmsudo rvm get stable
I get
rvmsudo: command not found
Googling the issue, does not resolve the problem.
RE: installtion issues - Added by Bernhard Rohloff almost 7 years ago
blackbeard . wrote:
So following this http://www.untrustedconnection.com/2018/01/redmine-passenger-and-nginx-on-ubuntu.html guide word for word, does not work. During the Ruby Installation, when I run
rvmsudo rvm get stable
I get
rvmsudo: command not found
Googling the issue, does not resolve the problem.
AFAIK there is no command rvmsudo.
I think the command should be
sudo rvm get stable
RE: installtion issues - Added by Mischa The Evil almost 7 years ago
Bernhard Rohloff wrote:
blackbeard . wrote:
[...]
rvmsudo rvm get stable
I get
rvmsudo: command not found
[...]
AFAIK there is no command rvmsudo. [...]
FWIW: that command does exist. See https://rvm.io/integration/sudo and https://github.com/rvm/rvm/blob/master/bin/rvmsudo. Its use is however only needed in very particular cases depending on how rvm is installed. Generally, its use is not needed as any user in the rvm group can already upgrade rvm itself.
blackbeard . .: The howto you're using tells you with this command to manually upgrade rvm itself (which earlier was installed from PPA) to the latest stable version, from the root user account. The error message says that rvmsudo couldn't be found in the path of the user account under which you're executing the command. You can confirm this by running:which rvmsudo
. It should output something like: /usr/local/rvm/bin/rvmsudo
or /usr/share/rvm/bin/rvmsudo
. Also try this for the rvm command itself. If neither give a proper result, it tells you that rvm hasn't been installed properly or you are executing the commands as the wrong user.rvm can be a bit tricky to install, as there is a lot that is involved. See https://rvm.io/rvm/install. The package that is used in the howto you are using comes preconfigured with some defaults. This might or might not fit your specific needs. Also, it is important to really logoff/login or even reboot the system if possible in some cases for all changes to take effect. Make sure you clearly understand the choices made for the rvm install and the whole howto in general, and act according to those.
If you keep experiencing these issues, I'd recommend to uninstall the packaged rvm, install rvm manually, tailored to your specific needs as explained in depth in the earlier linked install doc of rvm, and then continue with the howto where you were left off.
OT: I personally dislike/recommend against using tutorials/howto's for installing software like Redmine on a server as all of them come with a tight set of predefined choices, which are almost never clearly outlined upfront and sometimes even omitted completely. Besides, but related to, that, is that such a predefined setup removes the need for the administrator installing the software, to clearly think-through how the software is going to be deployed before the process is acually started. This, I think, is generally a bad tendency. I'm more of the school of: "know, tweak and control your stack, the whole stack". Especially certainly, if it's going to be used publicly and/or professionally. I'd say, start with answering the following question for (every part of) each software layer covering your complete stack: "what kind of setup is needed/required for my specific needs/use of the system?".
If you can't or don't want to get into that all, I'd recommend to 'outsource' it all to a specialized, third-party provider, which is in those cases usually also the safest for the system to be deployed.
RE: installtion issues - Added by Bernhard Rohloff almost 7 years ago
Mischa The Evil wrote:
Bernhard Rohloff wrote:
blackbeard . wrote:
[...]
rvmsudo rvm get stable
I get
rvmsudo: command not found
[...]
AFAIK there is no command rvmsudo. [...]
FWIW: that command does exist. See https://rvm.io/integration/sudo and https://github.com/rvm/rvm/blob/master/bin/rvmsudo. Its use is however only needed in very particular cases depending on how rvm is installed. Generally, its use is not needed as any user in the rvm group can already upgrade rvm itself.
Thank you Mischa for correcting me! Again what learned....
The pre-installed VMs from Bitnami could also be a way to go. For local use with a couple of colleagues this could be fine. But as Mischa mentioned above, one should definitely understand the underlying technology stack when Redmine is used in a bigger production environment.