kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss

Fork 0

Commit graph

Author	SHA1	Message	Date
Mayra Cabrera	0ab89d8e36	Add a rubocop for Rails.logger Suggests to use a JSON structured log instead Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102	2019-07-10 19:26:47 +00:00
Jan Provaznik	9ccf8d032f	Enabled feature flag for fast deletions Fast destroy is used only if the feature flag is enabled, otherwise uploads are still deleted using carrier wave. It's disabled by default.	2018-12-06 22:00:19 +01:00
Jan Provaznik	239fdc78b1	Use FastDestroy for deleting uploads 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.	2018-12-06 22:00:19 +01:00

Author

SHA1

Message

Date

Mayra Cabrera

0ab89d8e36

Add a rubocop for Rails.logger

Suggests to use a JSON structured log instead

Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102

2019-07-10 19:26:47 +00:00

Jan Provaznik

9ccf8d032f

Enabled feature flag for fast deletions

Fast destroy is used only if the feature flag is enabled, otherwise
uploads are still deleted using carrier wave. It's disabled by default.

2018-12-06 22:00:19 +01:00

Jan Provaznik

239fdc78b1

Use FastDestroy for deleting uploads

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.

2018-12-06 22:00:19 +01:00

3 commits