[GH-ISSUE #450] Use case suitabilty #242

New issue

Closed

opened 2026-03-04 01:43:36 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:43:36 +03:00

Owner

Originally created by @codecowboy on GitHub (Jul 14, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/450

I have some legacy code on a website which looks for video files to serve for download at an absolute path on file system. The disk is filling up and there is no money to rewrite the website code or buy expensive diskspace. Could I mount an s3 bucket using s3fs-fuse as a crude workaround to this problem? Could it handle concurrent file requests from apache?

Originally created by @codecowboy on GitHub (Jul 14, 2016). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/450 I have some legacy code on a website which looks for video files to serve for download at an absolute path on file system. The disk is filling up and there is no money to rewrite the website code or buy expensive diskspace. Could I mount an s3 bucket using s3fs-fuse as a crude workaround to this problem? Could it handle concurrent file requests from apache?

kerem closed this issue

2026-03-04 01:43:37 +03:00

kerem commented

2026-03-04 01:43:37 +03:00

Author

Owner

@ggtakec commented on GitHub (Jul 24, 2016):

@codecowboy
Probabry you can set a directory path for apache using to mountpoint by s3fs.

I think that there is no problem without performance.
But you only are care for that s3fs does not exclusive control for the file.

Please try to use s3fs for your apache working directories.
Regards,

@ggtakec commented on GitHub (Jul 24, 2016): @codecowboy Probabry you can set a directory path for apache using to mountpoint by s3fs. I think that there is no problem without performance. But you only are care for that s3fs does not exclusive control for the file. Please try to use s3fs for your apache working directories. Regards,

kerem commented

2026-03-04 01:43:37 +03:00

Author

Owner

@ggtakec commented on GitHub (Mar 30, 2019):

We kept this issue open for a long time.
I will close this, but if the problem persists, please reopen or post a new issue.

@ggtakec commented on GitHub (Mar 30, 2019): We kept this issue open for a long time. I will close this, but if the problem persists, please reopen or post a new issue.