我有一个GitLab社区版,并且向前惊人:)
推动回购 - 完成 从公共回购拉出 - 完成 克隆公共回购 - 完成如果我试图使回购的私有或内部,我不再能够克隆(应该是,开箱即用)
但是,为了Pete的缘故,我是如何“限制生产部署”(比如'web-user')并让这个用户在web服务器上调用git-server并克隆一个repo?
我已经尝试在GitLab上设置deploy-ssh,但这似乎是专门用于GitLab CI(我还没有开始):)
I have a GitLab Community Edition up and am staggering forward :)
Pushing to repos - DONE Pulling from public repos - DONE Cloning public repos - DONEif I try to make the repo's private or internal, I am no longer able to clone (as should be, out-of-the-box)
But how, for Pete's sake, am I to "cap production deploy" (as say 'web-user') and have this user on web-server call up git-server and clone a repo?
I've tried setting up deploy-ssh's on GitLab, but that seems to be dedicated to the GitLab CI (which I'm yet to embark) :)
最满意答案
GitLab repos有3个设置 - 与有资格克隆它们的用户有关 - 私有,内部和公共。 从Capfile中添加部署用户(或者您需要访问repo的那种方式)然后以该用户身份登录并添加其公共SSH密钥将使您进入repo - 只要您点击gitlab服务器上的正确IP-地址!
我的问题 - 事实证明 - 真的不是正确访问GitLab,而是从其他10.0.xx应用服务器点击10.0.xx-something而不是gitserver.some-domain.tld!
GitLab repos have 3 settings - pertaining to the users eligible to clone them - private, internal and public. Adding the deploy user from your Capfile (or which ever way you need access to the repo) and then logging in as that user and adding its public SSH key will get you to the repo - provided you hit the gitlab server on it's correct IP-address!
My question - it turned out - really was not about accessing GitLab correctly, but hitting 10.0.x.x-something instead of gitserver.some-domain.tld, from some other 10.0.x.x app-server!
更多推荐
发布评论