This sounds very interesting - thank you very much. As I have no idea about
the REST API, I wonder what happens if the database gets migrated (e.g.
from 7.x to 8.x) between project backup and restore. Does your software
taking care about this?
Regards
On Wednesday, 2 March 2016 10:57:09 UTC+1
Hi All,
since a few days my activity stream is not updating any more.
I already performed a *gitlab-rake gitlab:check* which showed all ok. Also
a cache clear with *gitlab-rake cache:clear* did not help. Can't see
anything suspicious in the production log.
I found the *proxy_temp* containing f
Check if you downloaded the correct version. Wheezy? Trusty? Precise? Or
whatever distro you are using.
I am on Trusty and upgraded recently from 7.13.2 to 7.13.4 without troubles.
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
To unsubscribe from t
I guess your request wont work. GitLab does have its own location where all
repositories are stored. The file permissions and hooks are managed by
GitLab... That is GitLab has some special hooks to make it work.
--
You received this message because you are subscribed to the Google Groups
"Git
I guess your request wont work. GitLab does have its own location where all
repositories are stored. The file permissions and hooks are managed by
GitLab... That is GitLab has some special hooks to make it work.
--
You received this message because you are subscribed to the Google Groups
"Git
I guess your request wont work. GitLab does have its own location where all
repositories are stored. The file permissions and hooks are managed by
GitLab... That is GitLab has some special hooks to make it work.
--
You received this message because you are subscribed to the Google Groups
"Git
I guess your request wont work. GitLab does have its own location where all
repositories are stored. The file permissions and hooks are managed by
GitLab... That is GitLab has some special hooks to make it work.
--
You received this message because you are subscribed to the Google Groups
"Git
I guess your request wont work. GitLab does have its own location where all
repositories are stored. The file permissions and hooks are managed by
GitLab... That is GitLab has some special hooks to make it work.
--
You received this message because you are subscribed to the Google Groups
"Git
I guess you are talking about multiple remotes? That is you can have your
repository on more than one server. The server you clone from is always the
origin. You can verify that by entering the command "git remote -v". You
can add other remotes (thus locations where your repo resides) by using
I agree with Bob. What can be nice for Readme files or similar, is unsafe
for code.
--
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.
The current implementation of "Project View" is not consistent with the
"Default Dashboard" view (all from profile settings).
When configuring (user profile) "Starred Projects" as the "Default
Dashboard" the Dashboard left selection strip shows the "Starred Projects"
and highlights this selecti
Try asking if your supplier is willing to increase the http timeout. Set
this parameter in the /etc/gitlab/gitlab.rb file:
# i think it is in seconds
unicorn['worker_timeout']='600'
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
To unsubscribe fro
I guess you are using http access?
--
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
ht
Another thing you can try: In your GitLab home folder look at:
./gitlab-rails/uploads/user/avatar//
Where you will get it from the database table "user" and
is the image name you uploaded. Also there must be a
./gitlab-rails/uploads/tmp// where is some unique number.
Just check if these fil
I facing similar problems that the user avatar or even the project logos
don't show up - but only sporadically. When reloading the page (F5) the
images then show up. I can only do guesswork here, but I looks to me like a
performance problem of GitLab not having enough RAM or CPU resources.
Can y
Usually a child process inherits the whole environment of its parent. The
hook you are running is a child process spawned from a parent, that spawns
another child process. Since parents do not inherit from childs you won't
get this to work.
You only chance is reading the commit hash and thus ex
effort somebody with me?
>
>
> Am Mittwoch, 10. Juni 2015 13:35:48 UTC+2 schrieb tombert:
>>
>> In GIT you can add as many remotes as you like and sync between them. But
>> this is no task of GitLab, this has to be configured in your local
>> repository:
>>
In GIT you can add as many remotes as you like and sync between them. But
this is no task of GitLab, this has to be configured in your local
repository:
https://help.github.com/categories/managing-remotes/
On Wednesday, 10 June 2015 08:21:55 UTC+2, Matthias Döring wrote:
>
> Hi, I can create a
Hi,
when I am subscribing to an issue, is there no way to find all issues which
I subscribed?
thx
--
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.
Now I see ...
There is no 386 distribution at all. Not even here:
https://about.gitlab.com/downloads/archives/
Seems that you have to upgrade to 64bit.
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
To unsubscribe from this group and stop rec
Dear Karen,
please have a look:
https://packages.gitlab.com/gitlab/gitlab-ce/ubuntu/dists/precise/main/binary-i386/Packages.gz
The package file is empty for the i386 distribution.
Regards
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
To unsubscri
These are the steps that made it work on my host:
https://groups.google.com/forum/#!topic/gitlabhq/QnfJNl7JIeM
--
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
Works for me in Ubuntu 14, Gitlab 7.9.1
Did you have a look at the log files?
--
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
Also had troubles, now I am doing this in gitlab.rb:
gitlab_rails['smtp_enable'] = true
gitlab_rails['smtp_address'] = "mailhost.myhost.at"
gitlab_rails['smtp_port'] = 25
#gitlab_rails['smtp_user_name'] = ""
#gitlab_rails['smtp_password'] = ""
#gitlab_rails['smtp_domain'] = "mydomain.at"
#gitlab_
You always push with the Gitlab user. You do not need an ssh account on the
server where Gitlab is installed resp. where the repos are stored.
For this to work you need to upload your ssh key in the profile, then use
the url gitlab@server:yourepo.git
--
You received this message because you are
I am on Ubuntu 14 LTS Desktop with Runner 5.1 - This Runner works.
Did not try 5.2.
Can you switch back to the old one?
--
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
Which OS are you using?
--
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
Update. Also check for valid e-mail strings:
--
#!/opt/gitlab/embedded/bin/ruby
# @backup
# Fix the PATH so that gitlab-shell can find git-upload-pack and friends.
ENV['PATH'] = '/opt/gitlab/bin:/opt/gitlab/embedded/bin:' + ENV['PATH']
#!/usr/bin/env ruby
refs = A
Might be related to this
one: https://gitlab.com/gitlab-org/gitlab-ce/issues/1271
--
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.co
Do you still have access to the database?
Just open the table application_settings, see the column signin_enabled and
put TRUE inside.
--
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,
See this post here:
https://groups.google.com/forum/#!topic/gitlabhq/pI_vKOc9O-E
Henry Gomez is implementing a bash hook, triggered on push events.
Here you see where to put these hooks:
http://doc.gitlab.com/ce/hooks/custom_hooks.html
Then I would recommend to try the git forums on how to find i
Would be great if you post how you got it working ... because the scripts
there are 7 months old, and since then GitLab changed the way hooks are
working.
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
To unsubscribe from this group and stop receiv
"I've been studying Gitlab hooks, but they seem to relate to commit events,
not repository creation."
Gitlab can react on pushes. Just an idea: you can initiate your custom hook
only after the initial push:
http://doc.gitlab.com/ce/hooks/custom_hooks.html
--
You received this message because
Yes they can be *bash *too as a *custom_hooks*, but I had the following
problem:
https://groups.google.com/forum/#!searchin/gitlabhq/custom_hooks/gitlabhq/bVt0JmX77Lw/nLD1whX8InEJ
So that's one reason why I stayed inside the main hook and not using
*custom_hooks*.
See the *custom_hooks* here:
ht
Maybe this could give you a head-start:
https://groups.google.com/forum/#!topic/gitlabhq/rzyuAXrKknQ
look for "git log" - you should easily also get the commit messages an be
able to reject afterwards.
--
You received this message because you are subscribed to the Google Groups
"GitLab" group.
GitLab has been designed to run from the main domain - thus it will
conflict with apache. There is nothing (simple) that I found that will
change that.
One thing you can do is putting GitLab on a different port and setup an
Apache redirect - look for gitlab.rb file.
GitLab should run on at leas
ame and home path.
>- how can I use same ssh-key to few repositories.
>- Is there anyway good tutorial.
>
> Thanks.
> בתאריך יום שישי, 20 בפברואר 2015 בשעה 07:49:05 UTC+2, מאת tombert:
>>
>> See here what you can do with *gitlab.rb*, which I guess
I now believe that redis and ruby all comes bundled in the omnibus
installer, so skipping the installation of those would be worth a try.
This page is also worth noting, showing all configuration
options:
https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-config-template/gitla
See here what you can do with *gitlab.rb*, which I guess you should find in
*/etc/gitlab/gitlab.rb*
https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/files/gitlab-config-template/gitlab.rb.template
You can define the port gitlab runs on by the following notation:
*http://host:port*
If
For those who want to install GitLab CI on Ubuntu 14 LTS, on the same
server as GiLab CE, here are the steps that made it work:
Install recommended packages defined here:
https://github.com/gitlabhq/gitlab-ci/blob/master/doc/install/installation.md
apt-get install wget curl gcc checkinstall libx
For those who want to install GitLab CI on Ubuntu 14 LTS, on the same
server as GiLab CE, here are the steps that made it work:
Install recommended packages defined
here:
https://github.com/gitlabhq/gitlab-ci/blob/master/doc/install/installation.md
#> sudo apt-get install wget curl gcc checkins
Hi,
basically I followed the instructions described here:
https://gitlab.com/gitlab-org/omnibus-gitlab/tree/master/doc/gitlab-ci
In etc/gitlab/gitlab.rb I added the following line:
ci_external_url 'http://myserver:82'
Note: GitLab CE is running on port 81.
Now when browsing to GitLab CI, port 8
I tried to create a new project with GitLab 7.6.2 but cannot confirm your
findings.
My project was created with a link to embedded/service/gitlab-shell/hooks
and a folder called hooks.old.141998367.
What it does not create is the custom_hooks folder - but that's not really
needed.
--
You recei
Hi,
*I posted already here but received no feedback:
https://forum.gitlab.com/t/puts-inside-custom-hooks/85*
Since the latest GitLab introduced custom_hooks: excerpt from pre-receive:
if GitlabAccess.new(repo_path, key_id, refs).exec &&
GitlabCustomHook.new.pre_receive(refs, repo_path) exit 0 e
GitLab is designed to work as the main host, there are ways to put GitLab
into a sub-folder but it is not recommended.
The way recommended is to set GitLab on a different port:
--- file /etc/gitlab/gitlab.rb
external_url 'http://:81'
Then setup a redirect on apache:
Require all grante
Update: encoding to UTF8 from database. Be less restrictive in checking
(reactivate code from first initial version)
--- file pre-receive
---
#!/opt/gitlab/embedded/bin/ruby
# @backup
# Fix the PATH so that gitlab-shell can find git-upload-
>
> You can try this server-side hook from me:
>
https://groups.google.com/forum/#!topic/gitlabhq/rzyuAXrKknQ
--
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
Because the "update" hook has been removed in GitLab version 7.4 here a new
and better reject hook replacing the pre-receive:
#!/opt/gitlab/embedded/bin/ruby
# @backup
# Fix the PATH so that gitlab-shell can find git-upload-pack and friends.
ENV['PATH'] = '/opt/gitlab/bin:/opt/gitlab/embedded/bin
Below the *update *ruby script from
*/opt/gitlab/embedded/service/gitlab-shell/hooks/update*
which does the trick. Note that I put a *.pgpass* file into the GitLab home
folder */var/opt/gitlab/*
-
#!/opt/gitlab/embedded/bin/ruby
# Fix the PATH so that gitlab-shell can find git-up
Hi,
before using GitLab I had a receive hook rejecting the push when the last
commit was from an unknown user.
So it was mandatory that they had user.name correctly configured - avoiding
commits from "dummy" users.
I would like to have the same hook in GitLab.
One idea would be directly accessi
Hi,
I am using GitLab 7 and seeking for a way to change the "Create New User"
defaults. Especially I want to set the can_create_group to false.
I hoped to be doing this using the /etc/gitlab/gitlab.rb file so that it
won't get lost when installing a new version.
thx
--
You received this mess
51 matches
Mail list logo
