| At line 13 changed one line |
| This allows you to connect to a Samba or Windows file server as the backend and provide the credentials. Usually in the format of "smb://user\domain:pass@servername/share/". |
| This allows you to connect to a Samba or Windows file server as the backend and provide the credentials. Usually in the format of "smb://domain\user:pass@servername/share/" or "smb://user@domain.com:pass@servername/share/". |
| At line 22 changed one line |
| (Disabled due to changes made by google. May come back at a later date after re-evaluating.) |
| Allows you to use google drive resources with Crush as the front end. Initial setup is not for the faint of heart though. [GDriveSetup] |
| At line 31 changed one line |
| Allows you to use a S3 bucket as the backend filesystem. However since S3 isn't hierarchical, you only get simulated folders, and no ability to rename, and some other gotchas about how S3 works. These aren't limitations we impose, but just due to the design decisions S3 made in that its intended for static item consumption and not as a location for holding and manipulating file names. |
| Allows you to use a S3 bucket as the backend filesystem. However since S3 isn't hierarchical, you only get simulated folders, and no ability to rename, and some other gotchas about how S3 works. These aren't limitations we impose, but just due to the design decisions S3 made in that its intended for static item consumption and not as a location for holding and manipulating file names.\\ |
| \\ |
| We support the IAM auth scenario too, its just not the default mode. Setting the S3 username to "iam_lookup" and S3 password to "lookup" will use this method.\\ |
| \\ |
| The following policy permissions are needed on S3:\\ |
| {{{ |
| s3:GetBucketLocation |
| s3:ListAllMyBuckets |
| s3:ListBucket |
| s3:ListBucketMultipartUploads |
| s3:PutObject |
| s3:AbortMultipartUpload |
| s3:ListMultipartUploadParts |
| }}} |
| At line 34 changed one line |
| This still uses an S3 bucket for storage, however we only use S3 as the storage for the object. We hold a special "s3" folder on the CrushFTP server which ahs the folder structure simulated, and "file" items which are XML pointers to the real S3 data. The difference is its *much* faster than the normal S3 since dir listings are fast, renames are instantaneous, etc. It uses S3 in the way it was designed for. The downside though is that if you make changes to the data in S3 and don't go through CrushFTP, now CrushFTP doesn't know what your data is in S3...your out of sync, and technically "corrupted". So if you want to sue S3 and have a fast and unlimited storage solution, S3Crush is perfect for that fi you won't be changing the data from another tool that hits the bucket directly. |
| This still uses an S3 bucket for storage, however we only use S3 as the storage for the object. We hold a special "s3" folder on the CrushFTP server which has the folder structure simulated, and "file" items which are XML pointers to the real S3 data. The difference is its *much* faster than the normal S3 since dir listings are fast, renames are instantaneous, etc. It uses S3 in the way it was designed for. The downside though is that if you make changes to the data in S3 and don't go through CrushFTP, now CrushFTP doesn't know what your data is in S3...you are out of sync, and technically "corrupted". So if you want to use S3 and have a fast and unlimited storage solution, S3Crush is perfect for that if you won't be changing the data from another tool that hits the bucket directly. |
