Uploads that survive a deploy
An app’s own folder is rebuilt on every deploy, so profile pictures, attachments and generated files saved there vanish the next time you push. A bucket keeps them apart from your code.
Buckets speak the S3 API, so there is no new library to learn: point django-storages, boto3, the AWS CLI or the AWS SDK at https://s3.rimbra.app with a Rimbra access key.
Three steps
- 1
Create a bucket in the dashboard.
- 2
Create an access key for all buckets or only this one, read and write or read only.
- 3
Add the endpoint, region auto and the key to your app’s settings. Django needs eight lines in settings.py.
Drop files or folders to upload, preview images, PDFs and text, rename, move and delete, and make links that expire after an hour, a day or a week.
Safe by default
- Buckets are private until you make one public. Private files need a key or a signed link that expires.
- Secrets are shown once and stored encrypted. Keys can be limited to some buckets and to reading.
- Files are served sandboxed, so an uploaded HTML or SVG file can’t run scripts.
Questions
Do I need to change my code?
Usually only settings. Any S3 client works once it uses the endpoint https://s3.rimbra.app, region auto and path-style addresses.
Can browsers upload straight to a bucket?
Yes. Make a presigned PUT URL on your server and add your site under the bucket’s CORS origins.
What does it cost past the allowance?
$0.03 per GB-month stored, $6.00 per million writes and $0.50 per million reads, paid from your balance. Downloads are free and don’t count toward your bandwidth.
What if my balance runs out?
Uploads pause until you top up. Files stay readable for 30 days, and we email you before it happens.
What if I cancel the add-on?
Reads and writes stop at once, but nothing is deleted. Add Buckets again and your files are back straight away.