e Procfile, same result...
>>>
>>> So how does the magic work and why is it not documented in your
>>> Troubleshooting catalog? :)
>>>
>>> Regards,
>>> Christoph Kretzschmar
>>>
>> --
> You received this message because you are subscrib
s://mygitlab
HTTP Clone URL: https://mygitlab/some-group/some-project.git
SSH Clone URL: git@mygitlab:some-group/some-project.git
Elasticsearch: no
Geo:no
Using LDAP: yes
Using Omniauth: yes
Omniauth Providers: saml
GitLab Shell
Version:3.2.1
Repository storage paths:
-
bump.
On Tue, Dec 6, 2016 at 12:45 PM, Alex Elman
wrote:
> I'm seeing a performance issue on my GitLab EE omnibus instance. Each
> branch DELETE gets processed by a unicorn worker. I have a 3 minute timeout
> on the unicorn workers and for some reason deletes often take more th
Does it work if you perform the rake task in your gitlab directory instead
of your gitlab-shell directory?
-Alex
On Thu, May 15, 2014 at 9:35 AM, Labbackup wrote:
> Ran the command from this page,
> https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/raketasks/backup_restore.mdand
> gett
You have an out-of-date init.d file. The installation.md document should
have outlined the steps for updating this file during the upgrade. If
you're on the 5-0-stable branch, try
sudo cp /home/git/gitlab/lib/support/init.d/gitlab /etc/init.d/gitlab
You can also link your init.d script so you don
I would caution against using git push -f. This could force a push that has
the potential to change upstream history. Downstream committers will be
very unhappy with you for doing that.
Are you sure you have Developer access or higher on that repo? You cannot
push to the repository if you have Gue
This is the gitlabhq mailing list. Are you looking for github perhaps?
On Tue, May 20, 2014 at 11:07 AM, Clare Barrington <
clarebarringtongould1...@gmail.com> wrote:
> I have only started receiving this error after I updated to the latest
> version. It doesn't seem to cause any issues however a
Please run
cd /home/git/gitlab
bundle exec rake gitlab:env:info RAILS_ENV=production
and
bundle exec rake gitlab:check RAILS_ENV=production
Please use something like https://gist.github.com/ to show us your results.
We can better assist with more context. Thanks!
-Alex
On Mon, May 19, 2014
Where is the root of your Gitlab installation?
-Alex
On Mon, May 19, 2014 at 2:42 PM, Labbackup wrote:
> I tried /home/git/ but there is no gitlab directory under there, just
> gitlab-shell
>
>
> On Friday, May 16, 2014 12:37:45 AM UTC-4, Alex Elman wrote:
>
>> Does it
I do not think that Administrators have this ability in the UI. You can
surface the feature request here http://feedback.gitlab.com/.
A workaround is to manually add the avatar in
/home/git/gitlab/public/uploads/user/avatar/. The directory names are the
user ids which you can gather from the datab
When performing an automerge, both parent commits must agree on a tree. It
sounds like this is not the case for you perhaps you should recreate your
satellite so it agrees with upstream's tree?
On Tue, May 20, 2014 at 2:45 PM, Renan Gurgel wrote:
> I have been finding some problem when I will ma
really should.
On Tue, May 20, 2014 at 9:55 PM, Alex Elman wrote:
> Where is the root of your Gitlab installation?
>
> -Alex
>
>
> On Mon, May 19, 2014 at 2:42 PM, Labbackup wrote:
>
>> I tried /home/git/ but there is no gitlab directory under there, just
>> git
so our structure looks nothing like this. I believe
> it is under /opt/gitlab-6.3.0.0/, key word is believe.
>
> On Wednesday, May 21, 2014 2:51:15 AM UTC-4, Alex Elman wrote:
>
>> In any case, the recommended directory structure for a Gitlab
>> installation should look roughly
try issuing ssh -T g...@git.blackcrafter.tk (or whatever the hostname is)
from your command prompt and respond with the reply from the server.
-Alex
On Sat, Jun 14, 2014 at 10:20 AM, Leonardo Medici
wrote:
> Hi, i recently installed Gitlab on Centos 6.5, i added my ssh-rsa key to
> my profile
Is it possible that you uploaded the private key to gitlab instead of the
public key?
-Alex
On Jun 23, 2014 6:39 PM, "Karl-Heinz Konrad"
wrote:
> Forgot to mention that the gitlab-rake checks all are green.
>
> On Monday, June 23, 2014 4:25:24 PM UTC-7, Karl-Heinz Konrad wrote:
>>
>> Hi all,
>>
Git proper doesn't have that kind of read granularity by virtue of the
distributed and decentralized nature of the repository. Even though Gitlab
allows for a centralized repository, there is no model available to control
read access to certain parts of a repository tree. Your best bet is to
either
Antsu,
Thank you for your investigation of the comparison bug. A Gitlab issue for
this bug was first opened here
https://github.com/gitlabhq/gitlabhq/issues/8174 21 days ago by GitHub user
lokeshkumar. I commented on that issue stating that I encountered the same
problem and that my investigation
Upgrading to v7.5.2 seemed to fix this issue for me. I don't have an
explanation yet, but I'll look into it.
On Tue, Nov 25, 2014 at 4:04 PM, James Riordon
wrote:
> I've deleted and blocked some accounts. This one account that used to be
> an admin account, and has created a few repos and posted
.
You do not have to upgrade, you just have to run the db migrations. In the
gitlab directory run bundle exec rake db:migrate RAILS_ENV=production.
-Alex
On Thu, Dec 4, 2014 at 11:52 AM, Alex Elman wrote:
> Upgrading to v7.5.2 seemed to fix this issue for me. I don't have an
> expl
It should be added that the events table requires that the updated_at and
created_at columns be not null. This constraint in the database will cause
the transaction to be rolled back and this ultimately caused the failure to
create the event model.
On Thu, Dec 4, 2014 at 12:17 PM, Alex Elman
What version of GitLab are you using? This functionality was fixed in
version 7.5.
On Thu, Dec 4, 2014 at 1:05 PM, wrote:
> I'm having a hard time figuring out when I should expect email
> notifications to be sent when adding a comment to a commit. I found the
> notification documentation here:
Nah you can just patch the restore code to not care about empty repos and
then try the restore again and it should work fine.
-Alex
On Mon, Dec 22, 2014 at 10:56 AM, Sytse Sijbrandij wrote:
> Since not being able to restore from backup is very serious we wonder
> if you could you contact supp..
22 matches
Mail list logo
