diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-10-07 18:06:24 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-10-07 18:06:24 +0000 |
| commit | eadb77d89f5f7d445bfd326f18873168f4719f12 (patch) | |
| tree | 207af6741c0f99f17345c1a28bc0c356740fefee /doc/raketasks | |
| parent | 31040b5bfe48f8d73830f473513164427522b3a6 (diff) | |
| download | gitlab-ce-eadb77d89f5f7d445bfd326f18873168f4719f12.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/raketasks')
| -rw-r--r-- | doc/raketasks/backup_restore.md | 4 | ||||
| -rw-r--r-- | doc/raketasks/list_repos.md | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/doc/raketasks/backup_restore.md b/doc/raketasks/backup_restore.md index 4a2afa5d5f9..fe9617c75ad 100644 --- a/doc/raketasks/backup_restore.md +++ b/doc/raketasks/backup_restore.md @@ -575,7 +575,7 @@ files. GitLab does not automatically prune old files stored in a third-party object storage (e.g., AWS S3) because the user may not have permission to list and delete files. We recommend that you configure the appropriate retention policy for your object storage. For example, you can configure [the S3 backup -policy as described here](http://stackoverflow.com/questions/37553070/gitlab-omnibus-delete-backup-from-amazon-s3). +policy as described here](https://stackoverflow.com/questions/37553070/gitlab-omnibus-delete-backup-from-amazon-s3). To schedule a cron job that backs up your repositories and GitLab metadata, use the root user: @@ -859,7 +859,7 @@ Be advised that, backup is successfully restored in spite of these warnings. The rake task runs this as the `gitlab` user which does not have the superuser access to the database. When restore is initiated it will also run as `gitlab` user but it will also try to alter the objects it does not have access to. Those objects have no influence on the database backup/restore but they give this annoying warning. -For more information see similar questions on PostgreSQL issue tracker[here](http://www.postgresql.org/message-id/201110220712.30886.adrian.klaver@gmail.com) and [here](http://www.postgresql.org/message-id/2039.1177339749@sss.pgh.pa.us) as well as [stack overflow](http://stackoverflow.com/questions/4368789/error-must-be-owner-of-language-plpgsql). +For more information see similar questions on PostgreSQL issue tracker[here](https://www.postgresql.org/message-id/201110220712.30886.adrian.klaver@gmail.com) and [here](https://www.postgresql.org/message-id/2039.1177339749@sss.pgh.pa.us) as well as [stack overflow](https://stackoverflow.com/questions/4368789/error-must-be-owner-of-language-plpgsql). ### When the secrets file is lost diff --git a/doc/raketasks/list_repos.md b/doc/raketasks/list_repos.md index 476428eb4f5..cfcf11cf3c2 100644 --- a/doc/raketasks/list_repos.md +++ b/doc/raketasks/list_repos.md @@ -15,7 +15,7 @@ sudo -u git -H bundle exec rake gitlab:list_repos RAILS_ENV=production If you only want to list projects with recent activity you can pass a date with the 'SINCE' environment variable. The time you specify is parsed by the Rails [TimeZone#parse -function](http://api.rubyonrails.org/classes/ActiveSupport/TimeZone.html#method-i-parse). +function](https://api.rubyonrails.org/classes/ActiveSupport/TimeZone.html#method-i-parse). ``` # Omnibus |