cannot pull/push/clone part of my (web) gitlab projects

2016-10-15 Thread X uboats
Hi, i'm a gitlab web user, and now meet some troubles
i'm using tortoisegit to push/pull/clone my gitlab projects

i have two projects. both are private, and one without any member but just 
me (non-coop). the other has several members as developer (coop, created by 
me).
the problem is that if i can pull/push for (coop) proj, then i cannot 
pull/push/clone for the other, and vice versa.

the error message always shows cannot find the url and xxx is not clean
the message appears for pull/push/clone my own proj (no coop)

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/f0c5c252-50a8-44fc-ae74-33a47429eff4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: GitLab SSH k

2016-10-15 Thread Aleksey Tsalolikhin
GitLab stores SSH keys in the file .ssh/authorized_keys  in the account of
the "git" user.

For example, I just spun up a GitLab CE instance and added an SSH key:

root@6986745c-ccbd-42ac-9498-deb8b37541d7:/var/opt/gitlab/.ssh# more
authorized_keys
command="/opt/gitlab/embedded/service/gitlab-shell/bin/gitlab-shell
key-1",no-po
rt-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty ssh-rsa
B3NzaC1yc
2EDAQABAAABAQDZuLDgFDf6Bgezk6nxS7QoRNtm3OiJWezm1/uJPxHqJKHJiiLhl0Iy400sSLzwL
EOAX0kQgHQ0XAtYjRd35+qzncU1mz07H4vxPD/VnQjY9M/74Xn8Qr3Jeuz4wI8zM4bBB9YGTab8Stao+
wKpuwXVZf9pQpV9PbeHEE2f+0tl/adwY3uBujXzbC+anwiksnuF80vld4veI4HOAWC+V7qjvGixa7pFC
XrUhRCw0DUBB85tcPH9qO7uC8dqrR8grPx6W37gav4nHmVv0eZNd6xVY4xEI6E+iXtKTvt9r35oIzoXM
SyPavSsI7nmtcY56Ya6fWQr7SFR1a3uLJzAxoy/
root@6986745c-ccbd-42ac-9498-deb8b37541d7:/var/opt/gitlab/.ssh#

Now let's take a peek in the database to see how keys are mapped to users:

root@6986745c-ccbd-42ac-9498-deb8b37541d7:~# su - gitlab-psql
$ /opt/gitlab/embedded/bin/psql --port 5432 -h /var/opt/gitlab/postgresql
-d gitlabhq_production
psql (9.2.18)
Type "help" for help.

gitlabhq_production=# \x
Expanded display is on.
gitlabhq_production=# select * from keys;
-[ RECORD 1
]---
id  | 1
user_id | 1
created_at  | 2016-10-15 13:43:43.871878
updated_at  | 2016-10-15 13:43:43.871878
key | ssh-rsa
B3NzaC1yc2EDAQABAAABAQDZuLDgFDf6Bgezk6nxS7QoRNtm3OiJWezm1/uJPxHqJKHJiiLhl0Iy400sSLzwLEOAX0kQgHQ0XAtYjRd35+qzncU1mz07H4vxPD/VnQjY9M/74Xn8Qr3Jeuz4wI8zM4bBB9YGTab8Stao+wKpuwXVZf9pQpV9PbeHEE2f+0tl/adwY3uBujXzbC+anwiksnuF80vld4veI4HOAWC+V7qjvGixa7pFCXrUhRCw0DUBB85tcPH9qO7uC8dqrR8grPx6W37gav4nHmVv0eZNd6xVY4xEI6E+iXtKTvt9r35oIzoXMSyPavSsI7nmtcY56Ya6fWQr7SFR1a3uLJzAxoy/
atsaloli@tashkent
title   | atsaloli@tashkent
type|
fingerprint | f2:c7:fe:89:f0:63:71:9e:8a:67:a9:49:a0:a4:99:2b
public  | f

gitlabhq_production=# select id, username from users;
-[ RECORD 1 ]--
id   | 1
username | root

gitlabhq_production=#

So there you go, you've got the key, the key title, and the user it belongs
to (root).

Hope this helps,
Aleksey Tsalolikhin
Vertical Sysadmin, Inc.
Authorized GitLab Training Partner


ᐧ

-- 
Need training on CFEngine, Git or Time Management?  Email
train...@verticalsysadmin.com.

On Fri, Oct 14, 2016 at 11:00 PM, Ashwini  wrote:

> Hi,
>
> How to get user and SSH key information using the SSH key finger print in
> Gitlab
>
> thanks
> Ashwini
>
> --
> You received this message because you are subscribed to the Google Groups
> "GitLab" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gitlabhq+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/gitlabhq/38ebf8ea-bead-4e02-9952-a5f5b090db09%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/CANNWuVW3Js80t0To1_3-VSoMJ9rHO4VAPd5gb0AdujPT1bGJ1g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: ldap account going through approval process ?

2016-10-15 Thread Aleksey Tsalolikhin
Perhaps run "sudo gitlab-ctl reconfigure" ?

ᐧ

-- 
Need training on CFEngine, Git or Time Management?  Email
train...@verticalsysadmin.com.

On Sat, Oct 15, 2016 at 12:19 AM, T.J. Yang  wrote:

> Thanks for the pointer to setting of block_auto_created_users.
>
> 1. set it to true and restart gilab 8.12.6
>
> [root@re02 ~]# grep block_auto_created_users /etc/gitlab/gitlab.rb
>   block_auto_created_users: true
> # block_auto_created_users: false
> # gitlab_rails['omniauth_block_auto_created_users'] = true
> [root@ilclsre02 ~]# gitlab-ctl restart
> ok: run: gitlab-workhorse: (pid 6661) 1s
> ok: run: logrotate: (pid 6673) 0s
> ok: run: nginx: (pid 6679) 0s
> ok: run: postgresql: (pid 6688) 1s
> ok: run: redis: (pid 6698) 0s
> ok: run: sidekiq: (pid 6714) 1s
> ok: run: unicorn: (pid 6719) 0s
> [root@re02 ~]#
>
> 2. Delete userA  from admin console
> 3. Ask userA to login again
>  3.1  step 2 and 3 are a few minutes apart.
> 4. userA was able to login and gitlab account auto recreated again.
>  4.1 from userA's profile page, userA is not locked.
>
> So this setting is not working,
>
>
> On Tuesday, October 11, 2016 at 3:36:53 PM UTC-5, T.J. Yang wrote:
>>
>> Hi
>>
>> I have ldap backend server configured and one can create gitlab account
>> automatically if the ldap account is valid.
>>
>> Is it possible the auto-create still going through administrator's
>> approval first then auto-create ?
>>
>>
>>
>> tj
>>
> --
> You received this message because you are subscribed to the Google Groups
> "GitLab" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gitlabhq+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/gitlabhq/e6361112-aa85-4d57-8ae2-1def435c0a67%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/CANNWuVVataR%2BVQSZZrMLVdQSyxdUWj1TbtLh2uzUWA2k%2BVpkYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: ldap account going through approval process ?

2016-10-15 Thread T.J. Yang
Thanks for the pointer to setting of block_auto_created_users.

1. set it to true and restart gilab 8.12.6

[root@re02 ~]# grep block_auto_created_users /etc/gitlab/gitlab.rb
  block_auto_created_users: true
# block_auto_created_users: false
# gitlab_rails['omniauth_block_auto_created_users'] = true
[root@ilclsre02 ~]# gitlab-ctl restart
ok: run: gitlab-workhorse: (pid 6661) 1s
ok: run: logrotate: (pid 6673) 0s
ok: run: nginx: (pid 6679) 0s
ok: run: postgresql: (pid 6688) 1s
ok: run: redis: (pid 6698) 0s
ok: run: sidekiq: (pid 6714) 1s
ok: run: unicorn: (pid 6719) 0s
[root@re02 ~]#

2. Delete userA  from admin console
3. Ask userA to login again
 3.1  step 2 and 3 are a few minutes apart. 
4. userA was able to login and gitlab account auto recreated again.
 4.1 from userA's profile page, userA is not locked.

So this setting is not working,


On Tuesday, October 11, 2016 at 3:36:53 PM UTC-5, T.J. Yang wrote:
>
> Hi
>
> I have ldap backend server configured and one can create gitlab account 
> automatically if the ldap account is valid.
>
> Is it possible the auto-create still going through administrator's 
> approval first then auto-create ?
>
>
>
> tj
>

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/e6361112-aa85-4d57-8ae2-1def435c0a67%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


GitLab SSH k

2016-10-15 Thread Ashwini
Hi,

How to get user and SSH key information using the SSH key finger print in 
Gitlab

thanks
Ashwini

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/38ebf8ea-bead-4e02-9952-a5f5b090db09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.