- 01 3月, 2014 4 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Backup Uploads Symlink
-
由 Dmitriy Zaporozhets 提交于
DB Reaping Frequency
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 28 2月, 2014 15 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Fix Backup Spec
-
由 Dmitriy Zaporozhets 提交于
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Sytse Sijbrandij 提交于
fixed typo at the user management help page
-
由 Jacob Vosmaer 提交于
Assuming that VERSION != VERSION.reverse is not robust. This will fail at e.g. version 6.6.6.
-
由 Dmitriy Zaporozhets 提交于
Issue Improve Ui
-
由 Jacob Vosmaer 提交于
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Postgres fixes For applications migrated from MySQL to PostreSQL it fixes some issues Fixes #1060
-
由 Dmitriy Zaporozhets 提交于
Use new gitlab_git gem. It makes CONTRIBUTING.md work
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 27 2月, 2014 21 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
由 Dmitriy Zaporozhets 提交于
-
由 Dmitriy Zaporozhets 提交于
Fixed attachment identifier displaying underneath note text
-
由 Dmitriy Zaporozhets 提交于
remove dead code: broken_diffs
-
由 Dmitriy Zaporozhets 提交于
Less strict backup versions
-
由 Stefan Wolf 提交于
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Jacob Vosmaer 提交于
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.
-
由 Dmitriy Zaporozhets 提交于
Pg Force Restore
-
由 Dmitriy Zaporozhets 提交于
-
由 Dmitriy Zaporozhets 提交于
Enable html_escape for code blocks highlighted in markdown Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/94
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 tsl0922 提交于
-
由 Dmitriy Zaporozhets 提交于
Fix backup/restore git hooks bug
-
由 Dmitriy Zaporozhets 提交于
Fixed typo in comments of apllication.scss
-
由 Dmitriy Zaporozhets 提交于
Updated changelog with my name for #6267
-
由 Robert Djurasaj 提交于
-
由 Jacob Vosmaer 提交于
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.
-