Creating and Configuring Containers

To create a new container:

  1. Under Cloud Storage, open the Containers section.
  2. Click New container.
  3. Enter a name for your container.
  4. Choose the container type.
  5. Click Save.

The new container will appear in the container list under the Containers tab.

Adding Files

There are two ways to add files and folders to containers:

  • Clicking the container name
  • Opening the container menu and selecting Container settings

Users with adequate permissions may also download the container as an archive or delete it.

By clicking the icon next to the container name, you can select one or more containers for deletion and then Delete (the bin icon). 

The container's contents will be displayed under the Files tab. There are no size limits for files uploaded to storage.

To add a file to your container, click Select file for upload or drag your file to designated area.

You can rename, copy, paste, and delete files in storage.

To delete a file, click Delete file.

In the open window, click Delete to confirm you would like to delete your file.

Creating and Configuring Folders in Containers

Subfolders can be created inside containers. Files in subfolders inherit the container's settings.

To create a folder, click the new folder icon, enter a name, and click Save.

You can rename, copy, paste, delete, and download folders as an archive.

Under the Folder settings tab, you can create a file upload link.

Link types:

  • Simple file upload
  • Upload with user-entered names
  • Add upload time to filename
  • Add uniq ID to filename
  • Upload to folder by date
  • Upload to folder by time
  • Upload to unique folder

Checking the box next to Password protect uploads will prompt you to create a password for your link.

Checking Time limits will open a date and time field. Files uploaded from your link will be deleted at this date/time.

Click Save to save any changes made to the folder settings.

Container Settings

A container's settings can be changed under the Container settings tab.

Privacy Settings

You can change the container type from the Container privacy settings block.

Cloud Storage offers two container types:

  • Private container - for saving backups and sensitive data, requires login and password
  • Public container - for distributing content for websites and apps, no authorization required

Container Limits

Various limits can bet set for you container from the Container limits block.

Here you can set limits on the number of files, total file size, and lifespan (time before files are automatically deleted) for files in the container.

Changes will come into effect after clicking Save.

Versioning

Instead of overwriting files, older versions can be saved in a separate container. You can activate this feature by opening the Versioning block and toggling the switch to Enable. You can then enter a custom container name where would-be-overwritten files will be saved.

Click Save to save your changes.

In the Upload link block, you can create a file upload link.

Link types:

  • Simple file upload
  • Upload with user-entered names
  • Add upload time to filename
  • Add uniq ID to filename
  • Upload to folder by date
  • Upload to folder by time
  • Upload to unique folder

Checking the box next to Password protect uploads will prompt you to create a password for your link.
Checking Time limits will open a date and time field. Files uploaded from your link will be deleted at this date/time.
Click Save to save your changes.

Special Pages

You can set an index or 404 error page in the Special pages block.

Index File Information

A special file will be returned for anonymous GET requests to the container name or its folders. You must enter the path to the file relative to your container's structure and given task.

Example:

Path: /index.html

Request: GET /container/, GET /container/dir1/

Response: /container/index.html

Path: index.html

Request: GET /container/

Response: container/index.html

Request: GET /container/dir1/dir2/

Response: /container/dir1/dir2/index.html, or (if no file) /container/index.html

404 Error Information

If an anonymous GET request is sent for a file that does not exist, a specific address will be returned with a specific code. If a 404 or 200 code is selected, the given file will be returned; if 307, the request will be redirected.

Examples:

Path: /404.html

Request: GET /container/nofile, GET /container/dir1/nofile

Response: /container/404.html

Path: 404.html

Request: GET /container/nofile

Response: /container/404.html

Request: GET /container/dir1/dir2/nofile

Response: /container/dir1/dir2/404.html or (if no file) /container/dir1/index.html or /container/index.html

Path: http://test.test

Request: GET /container/nofile, GET /container/dir1/nofile

Response: http://test.test

Information about the initial request can be transferred using automatic in-line template parameters:

  • {container} - container name
  • {path} path to file relative to container

Example:

404.php?redirect_from={container}/{path}

Web Listing Information

Enables file listing for the container. You can include a link to a style (CSS) file to customize your index.

 

Changes will come into effect after clicking Save.

HTTP headers

You can enter values for several HTTP headers in the HTTP headers block.

Expires

Description: Date when data expires

Common values:

Format: Day of th week (short), date (2 digits) Month (short) years hour:minute:second GMT

Example: Tue, 31 Jan 2012 15:02:53 GMT

Cache-Control

Description: Caching settings

Common values:

  • no-cache - disable caching
  • public - allows the local client and proxy server to cache webpages
  • private - allows caching only by the local client

Access-Control-Allow-Origin

Description: Allows cross-domain requests

Access-Control-Max-Age

Description: The maximum caching time (in seconds)

Access-Control-Allow-Methods

Description: Permitted request methods

Common values: GET, HEAD

 

Click Save to save your changes.

Managing Domains

Binding Domains

You can bind your domains to public containers. All of the files inside the container will be accessible from the bound domain. For example, if you bind the domain imgs.mysite.ru to the container mysite_imgs, then you will be able to access all of the files inside that container from http://imgs.mysite.ru/ (without entering the container name).

Important!

Please note that when you bind a domain, you have to add a DNS CNAME record for 193920.selcdn.ru. If you do not make these changes to the DNS, then the domain will not be bound. Information about changes to the DNS may not occur right away (they may take anywhere from a few hours to a few days), which is why the domain may have to be bound again when the DNS updates.

Second Level Domains

You can attach second level domains, like mydomain.org, to a container. To do this, you have to add A records to the DNS for each of the following IPv4 addresses: 188.93.16.235, 188.93.16.236, 188.93.16.237, 188.93.16.238. For IPv6 access, you will also have to add AAAA records to the DNS for each of the following IPv6 addresses: 2a00:ab00:0:12::235, 2a00:ab00:0:12::236, 2a00:ab00:0:12::237, 2a00:ab00:0:12::238

Disabling Domains

You can suspend domain access to a container by deleting the bound domain or changing the container type to private (by changing the container back to public, the files will again be accessible).

To bind domains, open the Domain management block and enter your domain name in the Bind domain field. Afterwards, click Bind.