Can somebody please point me to some talk or presentation on Gitlab
architecture and internals?
Thanks
--
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+unsu
Sorry, I meant to ask for a video presentation. Thanks for sharing that
anyway.
On Monday, February 6, 2017 at 9:22:54 PM UTC-8, Aleksey Tsalolikhin wrote:
>
> How's
> https://github.com/gitlabhq/gitlabhq/blob/master/doc/development/architecture.md
>
> ?
>
> On
I assumed that when you log in to GitLab with "Remember Me" not checked,
that when you close the browser and reopen it, you would have to log in
again. That doesn't appear to be the case. Is this a bug or does "Remember
Me" do something very different?
I am running gitlab-ce 7.12.2.
--
You re
On Thursday, July 9, 2015 at 3:37:59 PM UTC-4, Artsiom Shimanouski wrote:
>
> Hello
>
> I have dedicated server(ubuntu 14.04 +1.4.6) with VM(ubuntu 14.04 +
> nginx-1.8.0).
> I installed gitlab 7.12 to VM (with https). But for external access I must
> set up reverse-proxy on host server.
> How?
I am having a similar issue only none of my repos from github will import
it always says failed hours later.
On Wednesday, August 12, 2015 at 4:35:14 PM UTC-7, sytse wrote:
>
> Please try again.
>
>
> Best regards,
> Sytse 'Sid' Sijbrandij
> CEO GitLab B.V.
>
> On Wed, Aug 5, 2015 at 12:55 PM, Ma
So it has been a while. I was thinking about this again and noticed that
with 8.1.3, Remember Me still appears to do nothing. Not sure why that is.
On Thursday, July 16, 2015 at 9:32:15 AM UTC-4, Mike Clark wrote:
>
> I assumed that when you log in to GitLab with "Remember Me&q
logging in, I have one cookie "_gitlab_session" that expires in 1
week.
On Tuesday, October 27, 2015 at 3:15:57 PM UTC-4, Jeroen de Neef wrote:
>
> Remember Me works for me, is your browser accepting the cookies?
> Op 27 okt. 2015 19:41 schreef "Mike Clark" >:
>
>> S
n't
> remember you and clears the session cookie on browser shutdown.
>
> 2015-10-27 20:20 GMT+01:00 Mike Clark >
> :
>
>> So if you don't check "Remember Me", then log in, then close the browser
>> without logging out, when you go back to GitL
per_page=100&page=[n]
Is there some obvious thing that I'm missing here? Thanks,
Mike
--
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 gitlabh
All,
We recently purchased gitlab ee and started porting over from source safe.
Most of applications are written in legacy Visual Basic 6. One problem we
are finding is that during a merge request case sensitive issues are being
picked up and makes it hard for us to determine what was actually
We are running Gitlab 8.9.6 assigning most issues works fine. But a small
number of issues in one of our projects cannot be assigned.
Using the Gitlab website the spinner never goes away and I get the
following error in my JS http://gitlab/group/project/issues/466.json
net::ERR_CONTENT_LENGTH_
<==
2016/09/14 17:04:26 [error] 30125#0: *39 upstream prematurely closed
connection while reading upstream, client: 10.1.0.165, server: localhost,
request: "PUT /group/project_name/issues/735.json HTTP/1.1", upstream:
"http://unix:/var/opt/gitlab/gitlab-workhorse/socket:/group/pro
rdings from one paragraph to another. But really,
without a survey and looking over actual patterns of legal document editing
(even if just anecdotal), this is the purest speculation on my part.
Best,
--Mike Weilgart
--
You received this message because you are subscribed to the Google Groups
&q
The issue was caused by
https://gitlab.com/gitlab-org/gitlab-ce/issues/22664
Mike
On Wed, Sep 21, 2016 at 1:07 AM Drew Blessing wrote:
> This appears to be an error that occurs when a current/previous assignee
> no longer exists. There must have been a specific set of circumstances when
file; they are versions for your entire project. So unlike some other VCSes,
you can't just transfer the history of one file to become the new history of
another file and leave the rest of your project's history unaffected.
Does that answer your question?
Best,
—Mike Weilgart
Vertical
Git does not do rename tracking nor copy tracking, which means it doesn't record renames or copies. What it does instead is rename and copy detection.https://stackoverflow.com/q/16937359/5419599 might be useful for you also.
Best,—Mike WeilgartVertical Sysadmin, Inc.
On Dec 14, 2017, at 8:21
You can use the Gitlab API to get all the users
curl
"https://gitlab.company.com/api/v3/users?private_token=&per_page=100";
and for each user sudo with the user id to get the ssh key
curl
"https://gitlab.company.com/api/v3/user/keys?private_token=&sudo=11";
matching the key id with th
asked for a
username and password (no one specific) and every time, no matter the user,
I get "fatal: Authentication Failed"
I did notice that when I created a new git repo from scratch on the client,
I had no problem pushing to the server.
Any ideas on what might be causing my issues
Executing this line:
sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production
Gives this result:
rake aborted!
libicui18n.so.48: cannot open shared object file: No such file or directory
-
/home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/charlock_holmes-0.6.9.4/lib/charlock_holmes/charlock_
with no further
problems. :)
Cheers!
--
Mike Evans
Tel. 01603 812495
Fax. 08721 150308
Heaser Business Consulting Ltd
Registered Office
111 School Lane
Little Melton
Norwich
NR9 3LA
Company No. 4727238
Registered in England and Wales
-Original Message-
From: gitlabhq@googlegroup
20 matches
Mail list logo
