Documentation for:
Install N1ED plugin for TinyMCE
Install on server
PHP Laravel package
PHP Symfony package
PHP Composer package
PHP archived script
Node Express module
Node Nest module
Node custom integration
Standalone microservice
File manager debugging
Changelog
Stock images
Cloud storage
Amazon S3
S3-compatible (Custom)
Azure Blob
Custom CMS
Storing API key in DB
Set and change API key
Embed configuration widget
Multisite CMS
Multi-user app storages
Parent/child API keys
Admin API
Create API key
List API keys
Delete API key
Undelete API key
Set parent API key
Rotate API key
Rotate Admin API token
Editing configuration
UI, toolbar and widgets
CSS theming
File Manager
Image Editor
Bootstrap Editor
Bootstrap Blocks
Translator
YouTube
Chat GPT
API
Dynamic config
Call Flmngr from code

Connect an S3-compatible storage (Custom)

This article is related to N1ED Premium users who purchased an additional option to support cloud storages.

Besides Amazon S3, Flmngr works with any S3-compatible storage — Cloudflare R2, DigitalOcean Spaces, Wasabi, Backblaze B2, a self-hosted MinIO or rclone server, and more. You configure it in the same Cloud storages dialog of your dashboard: pick the storage, open Edit credentials, and switch the storage type from Amazon S3 to Custom.

The Custom form

  • Endpoint URL — the S3 API URL of your storage, e.g. https://<account>.r2.cloudflarestorage.com. Buckets are accessed in path style (endpoint/bucket/object), which every S3-compatible server supports.
  • Bucket — the bucket (or container/space) name. Create it on the provider side first.
  • Key / Secret — the access key id and secret. Most providers have a dedicated screen to create an S3 access key pair (e.g. R2 "API tokens", DigitalOcean "Spaces keys", Google "HMAC keys").
  • Server has no per-object ACL or folder markers — a checkbox for compatibility. Some servers do not implement per-object ACLs or empty-folder marker objects; without this box ticked, copy / move / rename and creating empty folders fail on them. Turn it on only for such servers (see the table).

Settings per provider

Provider Endpoint URL "No per-object ACL / folder markers" Notes
MinIO (self-hosted)https://minio.example.comOffFull S3 server. Create the bucket first.
rclone serve s3 (self-hosted)https://your-hostOnServes a plain directory as S3; no ACLs / markers.
Cloudflare R2https://<account>.r2.cloudflarestorage.comOnCreate an R2 API token for the key/secret.
DigitalOcean Spaceshttps://<region>.digitaloceanspaces.comOffe.g. sgp1, nyc3. Use a Spaces key pair.
Wasabihttps://s3.<region>.wasabisys.comOffFull S3 compatibility.
Backblaze B2https://s3.<region>.backblazeb2.comOffUse the S3-compatible application key.
Google Cloud Storagehttps://storage.googleapis.comOffNeeds HMAC interoperability keys. Note: deleting a folder is not supported over the S3 API — for full GCS support ask us about the native Google option.

Public file URLs

To display and download uploaded files, the storage must serve them publicly (like a public bucket), and your Flmngr configuration's urlFiles must point at that public base URL — usually <endpoint>/<bucket>/. This is the same urlFiles rule as for Amazon S3, and CORS still needs to allow your editor's origin so the image editor can read images.