Filebase File Storage
Adds Filebase as a file server type: decentralised storage behind an S3 endpoint, with direct downloads and uploads. Premium.
The Filebase plugin adds Filebase as a file server type. Filebase keeps your objects on decentralised storage networks behind an ordinary S3 endpoint, so BoxPuff talks to it exactly as it talks to Amazon: signed direct downloads, direct uploads from the browser, priority, geo and account-type targeting. The plugin fills in Filebase's endpoint and region; you type the key and the bucket.
Who it is for
Owners who like the idea of decentralised, redundant storage without running any of it themselves, and who want an S3 door to it that the site already understands. It can be the only server of a small site or one of several (File servers).
Switching it on
Premium plugin, key storage-filebase. Buy it on lcpanel.com, press Check again now on Admin → Configuration → License, then switch it on at Admin → Extensions → Plugins (the Manage Plugins page). The plugin's own settings page carries one How to use note: Add a file server under Infrastructure → File Servers and pick "Filebase" as its type. The keys, bucket and region are typed on that server, not here.
Adding the server
Open Admin → Infrastructure → File Servers, press Add File Server, and on the Add Storage Server page select Filebase as the Server Type. The page reads: Filebase puts your objects on decentralised networks behind an S3 endpoint. Make a bucket and an access key in the Filebase console.
| Field | What to type |
|---|---|
| Access Key, Secret Key | The access key pair from the Filebase console. |
| Bucket | The bucket you made there. |
| Region | us-east-1 - Filebase has the one region. |
| Endpoint | s3.filebase.com, already filled in. |
| Path-style URLs | Off. |
| Key Prefix | Optional folder inside the bucket, e.g. files/. |
| Direct Downloads | Yes = signed links straight from Filebase; No = streamed through the site. |
| Direct Uploads | Yes = browsers upload to Filebase in parallel pieces (CORS rule needed). |
| Public / CDN URL (optional) | A CDN in front of the bucket for public links. |
| Signed Link Lifetime | Seconds a signed link lives (3600). |
Name it with Server Label, set Status, review CDN Support, Storage Options (Max Storage, Server Priority), Geo Targeting and Account Type Targeting, and press Save and test. The test writes and removes a tiny object and reports the result.
Direct uploads
With Direct Uploads on, the browser asks the site for presigned parts and sends the file to Filebase itself; the site only records the finished file (Uploads). The bucket's CORS settings must allow it: the JSON rule is shown under CORS rule the bucket needs for direct uploads on the server form and on the S3 Connection Test page of the free Amazon S3 File Storage plugin. If the bucket refuses, the uploader falls back to the site's chunk.php road without the member noticing.
Downloads
A signed link lets the visitor pull the file from Filebase while your server only logs the download and applies the package rules. Site Settings → File Downloads → Direct bucket links only for unlimited speed streams speed-limited packages through the site instead, so a free account's cap still holds (Downloads).
Tips
- Decentralised storage can take a moment longer on the first byte than a hot bucket; it is a good fit for archives, backups and large downloads rather than for thumbnails - the previewer keeps its thumbnails in
uploads/thumbson the site anyway. - Uploads reach the server only when Site Settings → File Uploads chooses it (method, Default file server, priority).
- Use the S3 Connection Test page after changing a key; the site also pings and refreshes used space from the cron every five minutes (Scheduled jobs).
- If a test fails with a certificate complaint, see Troubleshooting: the server's CA bundle is usually the cause.