05 Mar, 2014
1 commit
-
Use new style shell commands
04 Mar, 2014
1 commit
03 Mar, 2014
2 commits
01 Mar, 2014
1 commit
-
Backup Uploads Symlink
27 Feb, 2014
5 commits
-
Previous to this commit, backups were tied to the git revision (SHA1) of the app at the time the backup:create command was invoked. If the SHA1 at the time of restore was different, the script would refuse to restore the backup. This commit loosens this tie so that the backup script only complains if the value of the Gitlab::VERSION constant is different between the time of backup and the time of restore.
-
Pg Force Restore
-
Enable html_escape for code blocks highlighted in markdown Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/94
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
26 Feb, 2014
4 commits
-
Fix backup/restore git hooks bug
-
The expected behavior during a GitLab backup restore is to overwrite existing database data. This works for MySQL because the output of mysqldump contains 'DROP TABLE IF EXISTS' statements. pg_dump on the other hand assumes that one will restore into an empty database. When this is not the case, during the restore with psql some of the data will be skipped if existing data is 'in the way'. By first invoking `rake db:schema:load` during a Postgres GitLab backup restore, we make sure that all important data is correctly restored.
-
The backup restore code for repositories was assuming that gitlab-shell is installed in /home/git/gitlab-shell. This commit changes that to use the configuration setting from gitlab.yml that specifies the path where gitlab-shell is installed.
-
The backup restore code moves any existing uploads directory out of the way before restoring the copy from the backup. If public/uploads was a symlink, this move would replace the symlink. This commit avoids this issue by first resolving any symlinks in the uploads path.
25 Feb, 2014
4 commits
18 Feb, 2014
5 commits
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Complete api files CRUD Adds ability to read file from repository with content encoded with Base64.
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
After update to recent grape env['api.format'] does not work any more. Use content_type for rendering raw json files content Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
17 Feb, 2014
1 commit
-
the existence of former ldap users doesn't imply LDAP is enabled.
13 Feb, 2014
2 commits
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
12 Feb, 2014
1 commit
-
add rake gitlab:import: all_users_to_all_groups and user_to_groups
11 Feb, 2014
1 commit
04 Feb, 2014
3 commits
-
Ensure directory exists before changing in popen
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
03 Feb, 2014
1 commit
31 Jan, 2014
1 commit
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
28 Jan, 2014
3 commits
-
ldap is disabled in the gitlab config, this fixes the API still calling the ldap backend.
-
Highlight.Js Replace pygments code highlight with client-side library - highlight.js http://highlightjs.org/
27 Jan, 2014
4 commits
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Upload Limits Better documentation for the upload limit. Please have a hard time when they need to change the upload limits, see https://gitlab.com/gitlab-org/gitlab-ce/issues/5
-
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>