|
I've used a hybrid of the notes from here and from here. Here's what I've done thus far: When I run the last command I get the following error: So the I created my mysql database and changed the values in config/database.yml to correlate with my newly created database values and got this error: So then I made some arbitrary database name values in the previous file and got these errors: [edit] Tried editing the redis.rb file after adding a custom app listening on a port. vim ~/.rvm/gems/ruby-1.9.3-p125/gems/redis-2.2.2/lib/redis.rb: bundle exec rake db:setup RAILS_ENV=production asked 10 Mar '12, 21:45 ArrantSquid |
|
NOTE: This procedure is out-dated and broken. DO NOT USE! You'll need a new ssh user and a custom app setup before you do anything. Remember the port you're given for your custom port. You'll be doing all of this as the new ssh user that you've created. Setup your ssh. On your client computer (your home machine): Now go onto your server with your ssh user: Now run this command to save yourself some headaches later: Now install gitolite: Then install some non-standard libraries (sqlite3 and redis): Now we need to configure redis: Install our ruby stuff and gitlab: Now we need to update our gitlab.yml file. Open the config/gitlab.yml editor (vim, emacs, nano): Change admin_uri to your ssh username and the urls you're using (eg gituser@git.asdf.com:gitolite-admin). Change the base path to reflect your ssh username (eg /home/gituser/repositories). Change your host to your host (eg git.asdf.com) and change your git_user to your ssh username. Uncomment the port. Continue setting up the gitlab stuff: Now you'll need to run: Now that that's running you've got a running install of gitlab. You'll need to point that custom app to a domain name, but once that's done you'll be good to go. Now just so you're aware after reading this, with 3 users logged into gitlab it takes up about 115mb of ram (just browsing no commits), so you need to be aware that it's a resource hog and you'll probably need to get extra ram (which is a problem with most RoR apps). Also, if you don't set the git config --global stuff and you add users, you'll screw up your install and have to re-install since it fails on that, but still adds the user. This was all figured out with the help of some awesome folks at webfaction who put up with about 56 messages from me with all of my very long and detailed output. So big thanks to Neerav K, Ryan S, Björn M, Todor K and Ilias R. You guys rock. answered 11 Mar '12, 04:21 ArrantSquid Were you able to successfully install gitlabhq in web faction? I am trying for the same and would like to know if these steps are followed in sequence, will it make ti happen? What is your personal experience using gitlabhq? Is it worth the installation?
(14 May '12, 02:27)
talktoari
I just wanted to make sure that if I start and follow that in order, I will be able to get it up and running in my web faction account. Let me know. Do I select Rails as the app while trying to create a new app in my web faction account? By default web faction has ruby 1.9.3 for the latest choice of rails app. Shall I chose that or do a custom installation of ruby 1.9.2p0? Will I be able to install all the libraries and packages needed or are they already installed in webfaction?
(14 May '12, 02:28)
talktoari
|
|
in part Install our ruby stuff and gitlab: echo "export PATH=$HOME/.rvm/bin:$PATH">>.bash_profile rvm install 1.9.2-p290 if you get -bash: rvm: command not found do source ~/.bash_profile and then try rvm install 1.9.3 it should work answered 18 Apr '12, 14:08 Manraj Singh Thanks for your comment, Manraj. I have incorporated the 'source' command into ArrantSquid's answer.
(11 Oct '13, 18:36)
likebike
|
|
I'm working through this and running into some issues, here: My guess is I've run off the rails (no pun intended) with a file folder specification somewhere. What I'm trying to figure out is, where do I fix the 'pointer' that is pointing to 'earleygitlab' and then gitlabhq, where it should be going straight to /gitlabhq. answered 08 Oct '13, 09:56 earleymw 1
Looks to me that you don't have your database.yml file setup in the correct location. "No such file or directory - /home/earleygitlab/gitlabhq/config/database.yml" Ruby is a fickle being. Which is why after I did all of this I promptly removed it all. It's a resource hog and it doesn't really buy you anything outside of a UI to stare at. That being said, a missing file would crash any app. Do an
(08 Oct '13, 17:44)
ArrantSquid
|
|
So based on the comment, I checked config and there was not a database.yml. I downloaded the sqlite3 one from a gist, but of course there is no support for it anymore, so i did cp config/database.yml.mysql2 config/database.yml I'm trying to install ANY database and continue getting errors. Note I've done as indicated and run install active-record...and also straight gem install mysql2. answered 10 Oct '13, 16:24 earleymw Please send us a support ticket so we can troubleshoot the issue further.
(12 Oct '13, 01:22)
johns
|
|
I documented the steps I took to get gitlab working... answered 09 Nov '14, 02:25 mogga The link returns a 404 :(
(22 Jan '15, 21:47)
pjrobertson
fixed. I changed my github username - sorry about that. Keep in mind this uses ALOT of ram.
(23 Jan '15, 04:25)
mogga
|
Here's what the directory structure for gitlabhq looks like (ls -a):
app .bundle CHANGELOG config config.ru db doc .foreman Gemfile Gemfile.lock .git .gitignore lib LICENSE log Procfile Procfile.production public .rails_footnotes Rakefile README.md resque_dev.sh resque.sh .rspec script spec .travis.yml vendor VERSION
I think I have successfully installed gitlab, but I am struggling with the last part of making a website point to my custom app. Since this is installed in a whole new user outside of the ~/webapps directory, how to I enable one of my domains to point to gitlab?
As long as you are using a "Custom Application (listening on port)" application type, then this is actually very straightforward. There is no specific binding to your main user account, and the only thing that matters is the port which your application is listening on.
Specifically, a Custom Application (listening on port) works by forwarding all requests to a localhost port. If, for example, the assigned port for your Custom Application is 12345, then incoming requests will be forwarded to 127.0.0.1:12345, and any application listening on this address and port can receive and handle that request. So, it doesn't matter at all where your Gitlab is installed to or which user it's running under - as long as it's binding to 127.0.0.1 and listening on the appropriate port, then it will work.
So, to answer your question - all you need to do is use a website record in the control panel to point your domain to the custom application (listening on port), and then configure your gitlab application to bind to 127.0.0.1 on the port assigned by that custom application.