From 3bf88211c33809b16afc60b4823a9b1c78929ebc Mon Sep 17 00:00:00 2001 From: "https://id.koumbit.net/anarcat" Date: Thu, 12 Feb 2015 16:43:41 +0000 Subject: [PATCH] --- doc/forum/original_filename_on_s3.mdwn | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/forum/original_filename_on_s3.mdwn b/doc/forum/original_filename_on_s3.mdwn index 2bd27aaaaa..7ecaab4e15 100644 --- a/doc/forum/original_filename_on_s3.mdwn +++ b/doc/forum/original_filename_on_s3.mdwn @@ -1,3 +1,5 @@ -I understand that S3 is seen as a "backend" storage mechanism, but since S3 files are available directly on the web, it would be nice to have the real filenames up there. +I understand that [[special_remotes/S3/]] is seen as a "backend" storage mechanism, but since S3 files are available directly on the web, it would be nice to have the real filenames up there. -Is there a way to set that up? I know about [[tips/publishing_your_files_to_the_public/]], but it assumes you have a local git repo with all the data in the first place, something which may not be available... --[[anarcat]] +Is there a way to set that up? I know about [[tips/publishing_your_files_to_the_public/]], but it assumes you have a local git repo with all the data in the first place, something which may not be available... + +my use case is that we have ~1TB of files already stored in S3 under specific filenames, and those filenames are how the files are accessed on the main website. changing all those filenames would be a significant burden... i'm not even sure this can be done cheaply on S3 in the first place. --[[anarcat]]