For public containers, you can now specify “special pages” - an index file and an error file. Index file - a page that will be displayed when a browser accesses a website address. The error file is the page that will be displayed if the user navigates to a nonexistent address.
To do this, in the container settings, it is enough to specify the file that will be used as an index file. The functionality of this option is very similar to the DirectoryIndex and index directives in Apache and Nginx, respectively. As a parameter, you can specify both the absolute path to the index file in the container and the relative path (without the “/” symbol at the beginning), then the path in the query will be taken into account when displaying the index file.
For example: the static site is located in the container “site”, the index file is “start.html”, the error file is “error.html”. When you go to the address “http://12345.selcdn.ru/site/” you will see the contents of the “start.html” page, and when you try to open the non-existing page “http://12345.selcdn.ru/site/qwerty. html ”the browser will be redirected to the page“ http://12345.selcdn.ru/site/error.html ”.
Custom page settings also work for container bound domains. Therefore, if the domain “www.site.test” was attached to the “site” container, then the behavior will be the same as for the default domain, and the name of the container itself will be hidden in the address.
To configure the error file, it is possible to specify the external address, and not just the file in the storage. For example, if you specify "http: //mysite.test/", then if you request a file that is not in the container, the user will be redirected to the address "http: //mysite.test/".
This feature allows you to easily and quickly place your static sites on the cloud storage. Based on the calculation of the cost of using the service, the placement of a static business card site will cost up to 10 rubles per month (with a fairly high attendance).
Previously, for those who were interested in how efficiently their storage works, only dry consumption figures were available. But the numbers are numbers - the graphics are much more interesting!
For each container, we added the ability to view the load on requests in the form of beautiful graphs of two types: the number of requests per second and outgoing traffic. Now you can clearly see for what money is written off.
Statistics can be viewed in the container settings (in the context menu in the right-most column of the list of containers).
The “objects-links” functionality is very similar to symbolic links in Unix systems and is suitable for several applications at once.
If you need to share with someone a file placed in a personal container, it is enough to create a special link to it. This will open access only to the desired file, without the need to change the type of access to the container or copy the file to a public container.
But that's not all! Links have a number of additional settings that can be combined as you like, namely:
Creating link objects is available not only through the control panel but also through the fully compatible OpenStack Swift API, which provides the basis for implementing sales mechanisms and / or individual access restriction to content for your sites and applications.
Now you can pay for the Cloud Storage service for the votes of the social network VKontakte. You can manage the service from the main service control panel (https://support.selectel.ru/storage/).
To start using the service for votes, you need to replenish the balance in the VKontakte application, then in the control panel (https://support.selectel.ru/storage/balance/) transfer the required number of votes to the balance, the translation is done at the rate of 1 vote = 5 rubles .
Source: https://habr.com/ru/post/165807/