# External storage
External storage works like adding a network drive to your computer. The uploaded files will be stored in this external storage rather than in your website local hard drive, which helps to leverage your server load and deliver a more reliable website.
# How does it works
Chevereto maps each image to the corresponding storage server using the given Storage URL to locate that file.
# URL Mapping
The storage URL will be used to "map" the uploaded images to the target storage URL by appending the file location to this URL. For example, if you set
https://storage.com/bucket/ as URL, it will map to
https://storage.com/bucket/the-file-path.jpg. You can completely customize this URL to map your storage scheme.
Chevereto only maps the URL to present a resulting image storage URL. The storage URL must resolve to the mapped URL
# Storage URL
The storage URL is the URL that Chevereto will use to map the files stored in the given storage. This could be the direct URL, a CNAME URL, a CDN URL or any URL that resolves the requested image. This means that you can customize the URL that you want to use for the storage. Is recommended that you use URLs that match your domain so try to take advantage of using a CNAME record.
# CDN over external storage
Since you can customize the storage URL you can easily add a CDN for each storage you want to use. You only need to go to your CDN provider and create a pull zone for the origin storage URL. So if you are using Amazon S3 the source or origin URL will be something like this:
So your CDN url will be something like this:
And a CNAME record will allow you to end up with something like this:
# dding a new external storage
If the storage credentials are correct the storage will be added and then you can toggle the activate checkbox to enable or disable that storage. When no storage is set to active the system will use the local storage.
# External storage APIs
# Amazon S3
- To setup Amazon S3:
- Create access credentials from Identity and Access Management console
- Click on "Create New Users", make sure to enable "Programmatic access"
- On permissions, associate AmazonS3FullAccess
- Store the user name, Access Key ID and Secret Access Key at the end of the process
- Create a bucket from the S3 console
- Click on "Create a Bucket" and proceed to create a bucket
- On permissions, make sure "Block new public ACLs" and "Remove public access" are unchecked (Public access settings)
- Store the bucket name and the region
- You don't need to setup logging
# S3 Compatible
The S3 Compatible API allows to upload images to any bucket implementing the S3 standard. The configuration is exactly the same as Amazon S3 but the storage isn't provided by Amazon.
# Backblaze B2
The FTP API allows to upload images to a server implementing the File Transfer Protocol.
The SFTP API allows to upload images to a server implementing the SSH File Transfer Protocol.
# Google Cloud
- To setup Google Cloud Storage:
- Create a project
- Go to "APIs & services" dashboard and make sure that "Google Cloud Storage JSON API" is enabled
- Go to "APIs & services" > "Credentials", click on "Create credentials" then click on "Service account key"
- Make sure to use the following settings:
- Select your service account or create a new one.
- Key type: JSON
- Your browser will start to download the JSON key file. Store the file contents.
- Go to "Storage" then click on "Browser"
- Create a bucket by clicking the "Create bucket" button. Store the bucket name.
The Local API allows to upload images to any filesystem path in the server.
# Microsoft Azure
- OpenStack configuration for RunAbove:
- Identity URL: https://auth.Runabove.io/v2.0
- Username: Your RunAbove username
- Password: Your RunAbove password
BHS-1This is the data center where your container was created
- Container: Name of your created container
- Tenant id: Leave it blank
- Tenant name: Your
project id, found on OpenStack Horizon on the left side (CURRENT PROJECT))
- URL: Your URL to access the container (see RunAbove CNAME)