I'm installing gitlab from source and I found this no 'gitaly' in bin folder. And 'bin' folder is totally missing in /home/git/gitalt/_build.
sudo -u git -H bundle exec rake "gitlab:gitaly:install[/home/git/gitaly,/home/git/repositories]" RAILS_ENV=production
I have run it without errors and no idea here.
Can you help me? Any comment is welcome.
Thank you.
Answer myself.
fixe it with changing account to git and doing without 'su'.
su - git && cd gitlab && bundle exec rake ...
Related
I have a problem with my Gitlab. After the installation it has no Layout.
When i try
bundle exec rake assets:precompile RAILS_ENV=production
It outputs
Could not locate Gemfile or .bundle/ directory
Gitlab is running on Debian with Apache. nginx is disabled.
from your directory run the following command
bundle install
if you see permission error the try above with command by appending "sudo"
You need to install rails app first then you can compile it's assets.
We use Gitlab in our project and we are planning to decommission the VM where our current GItlab is hosted and to move on to a different VM.
Is it possible to copy or duplicate the exact current set-up into our new VM along with its branches, tags and history? if so, could you pls. help me on the same.
Thanks !
Yes, it is possible.
This is what we did in our migration:
1.- In the new VM, clone the repo from the old VM.
cd /home/git/repositories/[your-namespace]/
git clone --bare git#old-git-vm:namespace/repo.git
2.- chown -R git:git repo.git
chmod 770 repo.git
3.- Import repos to Gitlab
sudo -u git -H bundle exec rake gitlab:import:repos RAILS_ENV=production
I'm trying to create a new project in 6.0. Gitlab says that repository was created successfully, but there is no repository created.
I was able to create project with repositories before. Suddenly these newly created repositories are not published on server.
Any help is highly appreciated!
Please switch in your gitlab install directory and run these commands to check your installation. Maybe something is not running:
sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
Following the 5.1 instructions to install gitlab
https://github.com/gitlabhq/gitlabhq/blob/master/doc/install/installation.md
When I run the command to test the install, I get an error "Git configured for user? ... no"
root#gitlab:/home/git/gitlab# sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
Checking Environment ...
Git configured for git user? ... no
Try fixing it:
sudo -u git -H git config --global user.name "GitLab"
sudo -u git -H git config --global user.email "gitlab#gitlab.ac"
For more information see:
doc/install/installation.md in section "GitLab"
Please fix the error above and rerun the checks.
Has python2? ... yes
python2 is supported version? ... yes
At no point in the instructions does it say to setup a user.name and user.email for the git user.
Can I safely ignore this warning, or should I deviate from the instructions and set it?
You are right it doesn't. This configuration is needed when you edit something from the web interface. I sent a pull request to include it in installation docs.
I recently set up a new VPS and have installed Git via yum and wget etc. All seemed well - I can add, commit, set up a remote and push to github.
However, when I try to pull from github:
user#domain.com [~]# git pull github master
git: 'pull' is not a git command. See 'git --help'.
Did you mean this?
shell
No, I didn't mean shell, I meant pull!
Now I've googled the heck outta this - including reading several posts on Stackoverflow:
"git pull" broken
git: 'pull' is not a git command. See 'git --help'
Although most posts seem to be about Mac issues (I'm on a CentOS server), it seems to be an issue with the git exec path, which is
user#domain.com [~]# git --exec-path
/usr/local/libexec/git-core
I've tried adding a various things to .bashrc with no success.
The key thing is that when I cd down to /usr/local/ and ls -l, I can't see a libexec directory.
But if I log in as root, I can cd to /usr/local/ and see libexec/, inside which is git-core. I can also git pull as root.
So - I suspect the problem is more to do with permissions and the server setup than git itself.
I've tried
sudo chmod a+rx /usr/local/libexec
But that did nowt too...
When I ssh into another server, as an account user, I can cd down to /usr/local and see libexec - so there's something wrong with this server setup.
Any ideas gratefully received.
Solved it now - the server is using jailshell... Disabling jailshell and using 'normal' shell works a treat