Selectel Storage Update
Thanks to everyone who participated in our survey . From the results of the survey, we selected the most requested functions and implemented them, namely:
This functionality was most in demand, as a really good service should be even more convenient and flexible. We recognize that the initial version with one user per account did not give options for companies consisting of a little more than one person (eg 1 administrator + + manager). The coder should keep statics, admin backups, the photo manager ... and none of them would like to share their innermost secrets with the others, but they don’t need it ... (although the manager’s photos, I think, would be interesting to her colleagues :)
Now you can create an additional user and specify for it one or more containers to which he will have access to write and read.
Additional users are completely independent / isolated from the main one, so you can block it, change the password, reassign containers.
Also, an additional user has the ability to perform any operations with objects in their containers, their metadata, as well as container metadata.
But there is a limitation, these users do not have access to the repository web interface, but only FTP access and API.
Second, but no less important: the functionality that is simply necessary when using the repository to distribute static content - management of container headers.
Now for public containers, you can specify the headers that will be attached to the content sent from it.
First, these are Cache-Control and Expires headers that affect end-user content caching and intermediate cache servers, which allows reducing traffic from the storage and improving site responsiveness to the end user.
Secondly, CORS headers that are needed for cross-domain queries.
Header management is available both through the control panel and through the REST API.
')
PS we also added the ability to store user vault passwords on our side, but this is only an option and should not be abused
- Additional users
- HTTP headers management
Additional users
This functionality was most in demand, as a really good service should be even more convenient and flexible. We recognize that the initial version with one user per account did not give options for companies consisting of a little more than one person (eg 1 administrator + + manager). The coder should keep statics, admin backups, the photo manager ... and none of them would like to share their innermost secrets with the others, but they don’t need it ... (although the manager’s photos, I think, would be interesting to her colleagues :)
Now you can create an additional user and specify for it one or more containers to which he will have access to write and read.
Additional users are completely independent / isolated from the main one, so you can block it, change the password, reassign containers.
Also, an additional user has the ability to perform any operations with objects in their containers, their metadata, as well as container metadata.
But there is a limitation, these users do not have access to the repository web interface, but only FTP access and API.
HTTP headers management
Second, but no less important: the functionality that is simply necessary when using the repository to distribute static content - management of container headers.
Now for public containers, you can specify the headers that will be attached to the content sent from it.
First, these are Cache-Control and Expires headers that affect end-user content caching and intermediate cache servers, which allows reducing traffic from the storage and improving site responsiveness to the end user.
Secondly, CORS headers that are needed for cross-domain queries.
Header management is available both through the control panel and through the REST API.
')
PS we also added the ability to store user vault passwords on our side, but this is only an option and should not be abused
Source: https://habr.com/ru/post/146948/
All Articles