delta/gitlab/gitlab-ce.git/app/models/uploads, branch docs/remove-cephfs-example gitlab.com: gitlab-org/gitlab-ce.git Add a rubocop for Rails.logger 2019-07-10T19:26:47+00:00 Mayra Cabrera mcabrera@gitlab.com 2019-07-10T19:26:47+00:00 0ab89d8e36ba58a95244b4c6dd49d53fac7a699f Suggests to use a JSON structured log instead Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102 
Suggests to use a JSON structured log instead

Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102
Enabled feature flag for fast deletions 2018-12-06T21:00:19+00:00 Jan Provaznik jprovaznik@gitlab.com 2018-12-04T19:48:21+00:00 9ccf8d032ff82841cdfe96e2abe4b1d317058244 Fast destroy is used only if the feature flag is enabled, otherwise uploads are still deleted using carrier wave. It's disabled by default. 
Fast destroy is used only if the feature flag is enabled, otherwise
uploads are still deleted using carrier wave. It's disabled by default.
Use FastDestroy for deleting uploads 2018-12-06T21:00:19+00:00 Jan Provaznik jprovaznik@gitlab.com 2018-10-07T18:31:08+00:00 239fdc78b1ced1861cdcf00b8927963e30ef2095 It gathers list of file paths to delete before destroying the parent object. Then after the parent_object is destroyed these paths are scheduled for deletion asynchronously. Carrierwave needed associated model for deleting upload file. To avoid this requirement, simple Fog/File layer is used directly for file deletion, this allows us to use just a simple list of paths. 
It gathers list of file paths to delete before destroying
the parent object. Then after the parent_object is destroyed
these paths are scheduled for deletion asynchronously.

Carrierwave needed associated model for deleting upload file.
To avoid this requirement, simple Fog/File layer is used directly
for file deletion, this allows us to use just a simple list of paths.