Tag Info

New answers tagged

2

Don't do it this way. Instead, use a config management system (Ansible, Saltstack, etc.). Keep those files in version control and use that the CM to deploy config changes to your servers. Doing things this way is highly beneficial in many ways: you have a full, offline backup of your server configurations, you can easily apply this configuration to ...


0

Oh sorry, this was my mistake. The problem with my configuration was, that I clone the repository via https_://dlock.../lw/bla which successfully worked, because of: location / { root /var/git; } But location ~ /git(/.*) { expects for sure: https_://dloc.../git/lw/bla to serve requests via smart http backend m(. If anyone stumbles upon same ...


-1

Step by step guide here. Alot of the solutions require a little bit of time. The refrenced link was the fastest way for me.


0

To Fix this we need to enable WebDav at apache server using 2 steps enable at vhost file of apache SetEnv GIT_PROJECT_ROOT /var/www/git SetEnv GIT_HTTP_EXPORT_ALL SetEnv REMOTE_USER=$REDIRECT_REMOTE_USER DocumentRoot /var/www/git <Directory /var/www/git> Options +ExecCGI +SymLinksIfOwnerMatch -MultiViews AllowOverride None ...


0

Adding the key the .ssh/known_hosts appears to be the right thing to do. Though when you automate the task you want to make sure the key is not already contained and added on each clone/pull tasks. This snippet will only add the fingerprint if not already found: if [ ! -n "$(grep "^bitbucket.org " ~/.ssh/known_hosts)" ]; then ssh-keyscan bitbucket.org ...


0

You can use the parameter force in vcsrepo, which will delete everything and recreate it for you. Docs


0

SSH by default will use the keys inside your .ssh directory. This is usually in ~/.ssh/. It seems you wrote the following command which may be a typo: ssh -C user@my_server 'cd /home/me/my_repo' && git pull The above command will run ssh, and after a successful completion (exit status 0), run git pull. I am just saying this as it may be related ...


0

In git version 2.3 there's an environment variable GIT_TERMINAL_PROMPT which when set to 0 will disable prompting for credentials. You can get more info about it in man git (after updating to git version 2.3) or in this blog post on github. Examples: git clone https://github.com/some/non-existing-repo will prompt for username & password ...


0

It isn't the same, and I wish someone would submit patches to etckeeper to support pkg, but an alternative might be to just snapshot the entire filesystem, if your /etc is on zfs.


1

With Gitlab, You can clone via HTTP or via SSH. Which URL do you use ? via HTTP(S), you must provide the login/password from your GitLab UI account. via SSH, you must configure correctly SSH on your client : first try to keep your private key (corresponding to the public key configured in your GitLab account) at the default place where SSH will search for ...


1

YES, Usually corporate networks are behind proxy. Try to find your git repo server public IP (google it), ping it. If it isn't working you are probably behind a proxy server. If you are behind proxy use: git config --global http.proxy http://proxy_address:proxy_port git clone http://.../.. You can find proxy address in internet explorer ...


1

I often use an external, browser based, dns/ip lookup tool, like GetIP, to get the ip address of a server I'm trying to connect to. Then you can use the address for git, svn, etc as long as it's not explicitly blocked by your corporate firewall or proxy.



Top 50 recent answers are included