Skip to main content

Manage Files via Console

This document will guide you on how to comprehensively manage cloud storage through the Cloud Development Console, including core features such as file management, permission settings, and cache configuration.

Quick Access

You can perform all cloud storage-related operations on the CloudBase Console - Cloud Storage page.

File Management

Through the file management feature, you can conveniently view and manage all files in cloud storage:

  1. Go to the File Management page to view the list of all files in your cloud storage space.
  2. Click the file name or the "Details" button to view detailed file information.

File Management Interface

Permission Settings

Cloud Storage permission settings allow you to control who can access your files:

  1. Go to the Permission Settings page
  2. Based on your business requirements, select the appropriate storage permissions and save them.
  3. You can also achieve more granular permission control via Custom Security Rules.

Permission Settings Interface

Cache Configuration

Cache Configuration Overview

The cache configuration feature of Cloud Storage can help you optimize file access performance and save bandwidth costs:

  • Files in cloud storage have CDN acceleration enabled by default. You can control CDN expiration rules through cache configuration.
  • Properly configuring cache time can effectively increase the hit rate, reduce the origin fetch rate, and save bandwidth costs.
  • How CDN cached resources work:
    • Unexpired resources: User requests are returned directly from CDN nodes, improving access speed
    • Expired resources: CDN nodes need to retrieve the content again from the origin server, then cache and return it to users

Configure cache rules

Follow the steps below to configure cache rules for cloud storage:

  1. Go to the Cache Configuration page

  2. Click the "Edit Cache Configuration" button to add custom cache rules based on the default configuration

    The default configuration is: all files are cached for 2 minutes

  3. Select one of the following three configuration methods:

    Configuration MethodDescriptionExample
    By file typeSet cache time for files with specific extensions.png, .jpg, .php
    By folderSet cache time for all files under specific folders/images/, /static/
    By fileSet cache time for specific files or file patterns/test/abc/*.jpg
  4. Configuration Rules Description:

    • You can enter multiple configurations, each separated by a semicolon (;).
    • Content is case-sensitive
    • File types must start with ., and folders must start with /
    • When the cache time is set to 0, it means no caching, and all requests will be forwarded to the origin server.
    • The maximum cache time cannot exceed 365 days.
  5. Click the 'Save' button to complete the configuration. The deployment process will take approximately 5 minutes.

Important

During the configuration deployment process, if you edit the cache configuration again, it will overwrite the previous configuration. The system will take the last deployment result as the final configuration.

Cache policy priority

When configuring multiple cache policies, note the following priority rules:

  • In the configuration list, policies at the bottom have higher priority than those at the top
  • You can adjust the priority of each policy by dragging the move icon in front of the list.
  • When multiple policies match a resource simultaneously, the last matched policy will be applied.

Priority Example

Assume a domain has the following cache rules configured:

PriorityTargetCache Duration
5 (Lowest)All files2 minutes
4.php .jsp .aspx0 seconds
3.jpg .png .gif300 seconds
2/test/*.jpg400 seconds
1 (Highest)/test/abc.jpg200 seconds

When accessing the resource www.test.com/test/abc.jpg, the matching process is as follows:

  1. Match the "All files" rule → hit, cache duration is 2 minutes.
  2. Match the ".php .jsp .aspx" rule → miss
  3. Match the ".jpg .png .gif" rule → hit, cache duration updated to 300 seconds.
  4. Match the "/test/*.jpg" rule → hit, cache duration updated to 400 seconds.
  5. Match the "/test/abc.jpg" rule → hit, cache duration finally determined as 200 seconds.

Final result: The cache duration of this resource is 200 seconds because the last matched rule has the highest priority.