- 19 Feb, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
This reverts commit 7d5f86f6.
-
- 16 Feb, 2015 1 commit
-
-
Hannes Rosenögger authored
This commit moves the note folder from /public/uploads/note to /uploads/note and changes the uploader accordingly. Now it's no longer possible to avoid the access control by modifing the url. The Avatar upload has been refactored to use an own uploader as well to cleanly seperate the two upload types.
-
- 20 Nov, 2014 1 commit
-
-
Jacob Vosmaer authored
-
- 01 Oct, 2014 1 commit
-
-
Jacob Vosmaer authored
This change also shows the output of failed Git commands during the backup.
-
- 29 Sep, 2014 1 commit
-
-
Jacob Vosmaer authored
-
- 08 May, 2014 1 commit
-
-
Jacob Vosmaer authored
Fixes a bug with non-UTF8 locales introduced by 2b816075.
-
- 03 Mar, 2014 1 commit
-
-
Jacob Vosmaer authored
-
- 27 Feb, 2014 1 commit
-
-
Jacob Vosmaer authored
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.
-
- 06 Nov, 2013 2 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
- 05 Aug, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 03 Jun, 2013 1 commit
-
-
Angus MacArthur authored
-
- 30 May, 2013 1 commit
-
-
Angus MacArthur authored
These fixes will allow a restore of gitlab when the backups and repositories directories are in non-standard locations (ie sub-dirs of gitlabhq). Also allows the restore to be run from script overriding the need of a user to confirm the rebuild of the authorized_keys file.
-
- 08 May, 2013 1 commit
-
-
Lev Abalkin authored
-
- 06 May, 2013 1 commit
-
-
Lev Abalkin authored
-
- 05 May, 2013 1 commit
-
-
Andrey Kumanyaev authored
-
- 23 Apr, 2013 1 commit
-
-
Angus MacArthur authored
If the backup directory is not sub the gitlab install directory, then the git rev-parse call will fail.
-
- 18 Apr, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 10 Apr, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 05 Apr, 2013 2 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 14 Mar, 2013 1 commit
-
-
Chris Lawlor authored
Uses ActiveRecord::Base.connection.quote_table_name. Fixes issue 2437.
-
- 11 Feb, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 05 Jan, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 31 Dec, 2012 2 commits
-
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
-
- 23 Dec, 2012 1 commit
-
-
Riyad Preukschas authored
-
- 22 Dec, 2012 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 20 Dec, 2012 2 commits
-
-
Riyad Preukschas authored
Rename gitlab:app:db_* to gitlab:backup:db:* Rename gitlab:app:repo_* to gitlab:backup:repo:* Rename *_dump to *_create
-
Riyad Preukschas authored
-
- 22 Nov, 2012 1 commit
-
-
Gosuke Miyashita authored
In backup_create, backup information hash is using symbol as its key. But in backup_restore, string key is used and it returns empty value.
-
- 19 Nov, 2012 1 commit
-
-
Hugo Duksis authored
-
- 26 Sep, 2012 1 commit
-
-
Nihad Abbasov authored
-
- 02 Sep, 2012 1 commit
-
-
Sytse Sijbrandij authored
Merge branch 'master' into non-interactive-aws-install Conflicts: doc/installation.md Fix merge mess in installation.md
-
- 28 Aug, 2012 2 commits
- 25 Aug, 2012 1 commit
-
-
randx authored
-
- 27 Jul, 2012 1 commit
-
-
Michael van Rooijen authored
-
- 26 Jul, 2012 1 commit
-
-
Michael van Rooijen authored
Modified the `repo_dump` and `repo_restore` rake tasks to properly dump and restore repositories based on their `path` rather than their (project) `name`. The project name can be uppercase and may contain spaces. This caused the repository to be restored as a different `path` that it was initially created as, thus, breaking the `git remote` and the web interface can no longer detect the repository either because it searches by `path` and not by `name`. Also, when restoring the permissions are incorrect making it impossible to push new commits to the remote repository. So now on success it'll set the correct permissions (but requires that the `gitlab` user has `sudo` privileges, or this task must be executed as root).
-
- 18 Jul, 2012 1 commit
-
-
Michael Richardson authored
-