Malin/WPS3Media
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add S3-compatible storage provider (MinIO, Ceph, R2, etc.)

Browse Source 
Adds a new 'S3-Compatible Storage' provider that works with any
S3-API-compatible object storage service, including MinIO, Ceph,
Cloudflare R2, Backblaze B2, and others.

Changes:
- New provider class: classes/providers/storage/s3-compatible-provider.php
  - Provider key: s3compatible
  - Reads user-configured endpoint URL from settings
  - Uses path-style URL access (required by most S3-compatible services)
  - Supports credentials via AS3CF_S3COMPAT_ACCESS_KEY_ID /
    AS3CF_S3COMPAT_SECRET_ACCESS_KEY wp-config.php constants
  - Disables AWS-specific features (Block Public Access, Object Ownership)
- New provider SVG icons (s3compatible.svg, -link.svg, -round.svg)
- Registered provider in main plugin class with endpoint setting support
- Updated StorageProviderSubPage to show endpoint URL input for S3-compatible
- Built pro settings bundle with rollup (Svelte 4.2.19)
- Added package.json and updated rollup.config.mjs for pro-only builds
This commit is contained in:
Malin
2026-03-03 12:30:18 +01:00
commit 3248cbb029
2086 changed files with 359427 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

272
vendor/Gcp/google/common-protos/src/Api/RoutingParameter.php vendored Normal file
View File

@@ -0,0 +1,272 @@
<?php
# Generated by the protocol buffer compiler. DO NOT EDIT!
# source: google/api/routing.proto
namespace DeliciousBrains\WP_Offload_Media\Gcp\Google\Api;
use DeliciousBrains\WP_Offload_Media\Gcp\Google\Protobuf\Internal\GPBType;
use DeliciousBrains\WP_Offload_Media\Gcp\Google\Protobuf\Internal\RepeatedField;
use DeliciousBrains\WP_Offload_Media\Gcp\Google\Protobuf\Internal\GPBUtil;
/**
* A projection from an input message to the GRPC or REST header.
*
* Generated from protobuf message <code>google.api.RoutingParameter</code>
*/
class RoutingParameter extends \DeliciousBrains\WP_Offload_Media\Gcp\Google\Protobuf\Internal\Message
{
/**
* A request field to extract the header key-value pair from.
*
* Generated from protobuf field <code>string field = 1;</code>
*/
protected $field = '';
/**
* A pattern matching the key-value field. Optional.
* If not specified, the whole field specified in the `field` field will be
* taken as value, and its name used as key. If specified, it MUST contain
* exactly one named segment (along with any number of unnamed segments) The
* pattern will be matched over the field specified in the `field` field, then
* if the match is successful:
* - the name of the single named segment will be used as a header name,
* - the match value of the segment will be used as a header value;
* if the match is NOT successful, nothing will be sent.
* Example:
* -- This is a field in the request message
* | that the header value will be extracted from.
* |
* | -- This is the key name in the
* | | routing header.
* V |
* field: "table_name" v
* path_template: "projects/&#42;&#47;{table_location=instances/&#42;}/tables/&#42;"
* ^ ^
* | |
* In the {} brackets is the pattern that -- |
* specifies what to extract from the |
* field as a value to be sent. |
* |
* The string in the field must match the whole pattern --
* before brackets, inside brackets, after brackets.
* When looking at this specific example, we can see that:
* - A key-value pair with the key `table_location`
* and the value matching `instances/&#42;` should be added
* to the x-goog-request-params routing header.
* - The value is extracted from the request message's `table_name` field
* if it matches the full pattern specified:
* `projects/&#42;&#47;instances/&#42;&#47;tables/&#42;`.
* **NB:** If the `path_template` field is not provided, the key name is
* equal to the field name, and the whole field should be sent as a value.
* This makes the pattern for the field and the value functionally equivalent
* to `**`, and the configuration
* {
* field: "table_name"
* }
* is a functionally equivalent shorthand to:
* {
* field: "table_name"
* path_template: "{table_name=**}"
* }
* See Example 1 for more details.
*
* Generated from protobuf field <code>string path_template = 2;</code>
*/
protected $path_template = '';
/**
* Constructor.
*
* @param array $data {
* Optional. Data for populating the Message object.
*
* @type string $field
* A request field to extract the header key-value pair from.
* @type string $path_template
* A pattern matching the key-value field. Optional.
* If not specified, the whole field specified in the `field` field will be
* taken as value, and its name used as key. If specified, it MUST contain
* exactly one named segment (along with any number of unnamed segments) The
* pattern will be matched over the field specified in the `field` field, then
* if the match is successful:
* - the name of the single named segment will be used as a header name,
* - the match value of the segment will be used as a header value;
* if the match is NOT successful, nothing will be sent.
* Example:
* -- This is a field in the request message
* | that the header value will be extracted from.
* |
* | -- This is the key name in the
* | | routing header.
* V |
* field: "table_name" v
* path_template: "projects/&#42;&#47;{table_location=instances/&#42;}/tables/&#42;"
* ^ ^
* | |
* In the {} brackets is the pattern that -- |
* specifies what to extract from the |
* field as a value to be sent. |
* |
* The string in the field must match the whole pattern --
* before brackets, inside brackets, after brackets.
* When looking at this specific example, we can see that:
* - A key-value pair with the key `table_location`
* and the value matching `instances/&#42;` should be added
* to the x-goog-request-params routing header.
* - The value is extracted from the request message's `table_name` field
* if it matches the full pattern specified:
* `projects/&#42;&#47;instances/&#42;&#47;tables/&#42;`.
* **NB:** If the `path_template` field is not provided, the key name is
* equal to the field name, and the whole field should be sent as a value.
* This makes the pattern for the field and the value functionally equivalent
* to `**`, and the configuration
* {
* field: "table_name"
* }
* is a functionally equivalent shorthand to:
* {
* field: "table_name"
* path_template: "{table_name=**}"
* }
* See Example 1 for more details.
* }
*/
public function __construct($data = NULL)
{
\DeliciousBrains\WP_Offload_Media\Gcp\GPBMetadata\Google\Api\Routing::initOnce();
parent::__construct($data);
}
/**
* A request field to extract the header key-value pair from.
*
* Generated from protobuf field <code>string field = 1;</code>
* @return string
*/
public function getField()
{
return $this->field;
}
/**
* A request field to extract the header key-value pair from.
*
* Generated from protobuf field <code>string field = 1;</code>
* @param string $var
* @return $this
*/
public function setField($var)
{
GPBUtil::checkString($var, True);
$this->field = $var;
return $this;
}
/**
* A pattern matching the key-value field. Optional.
* If not specified, the whole field specified in the `field` field will be
* taken as value, and its name used as key. If specified, it MUST contain
* exactly one named segment (along with any number of unnamed segments) The
* pattern will be matched over the field specified in the `field` field, then
* if the match is successful:
* - the name of the single named segment will be used as a header name,
* - the match value of the segment will be used as a header value;
* if the match is NOT successful, nothing will be sent.
* Example:
* -- This is a field in the request message
* | that the header value will be extracted from.
* |
* | -- This is the key name in the
* | | routing header.
* V |
* field: "table_name" v
* path_template: "projects/&#42;&#47;{table_location=instances/&#42;}/tables/&#42;"
* ^ ^
* | |
* In the {} brackets is the pattern that -- |
* specifies what to extract from the |
* field as a value to be sent. |
* |
* The string in the field must match the whole pattern --
* before brackets, inside brackets, after brackets.
* When looking at this specific example, we can see that:
* - A key-value pair with the key `table_location`
* and the value matching `instances/&#42;` should be added
* to the x-goog-request-params routing header.
* - The value is extracted from the request message's `table_name` field
* if it matches the full pattern specified:
* `projects/&#42;&#47;instances/&#42;&#47;tables/&#42;`.
* **NB:** If the `path_template` field is not provided, the key name is
* equal to the field name, and the whole field should be sent as a value.
* This makes the pattern for the field and the value functionally equivalent
* to `**`, and the configuration
* {
* field: "table_name"
* }
* is a functionally equivalent shorthand to:
* {
* field: "table_name"
* path_template: "{table_name=**}"
* }
* See Example 1 for more details.
*
* Generated from protobuf field <code>string path_template = 2;</code>
* @return string
*/
public function getPathTemplate()
{
return $this->path_template;
}
/**
* A pattern matching the key-value field. Optional.
* If not specified, the whole field specified in the `field` field will be
* taken as value, and its name used as key. If specified, it MUST contain
* exactly one named segment (along with any number of unnamed segments) The
* pattern will be matched over the field specified in the `field` field, then
* if the match is successful:
* - the name of the single named segment will be used as a header name,
* - the match value of the segment will be used as a header value;
* if the match is NOT successful, nothing will be sent.
* Example:
* -- This is a field in the request message
* | that the header value will be extracted from.
* |
* | -- This is the key name in the
* | | routing header.
* V |
* field: "table_name" v
* path_template: "projects/&#42;&#47;{table_location=instances/&#42;}/tables/&#42;"
* ^ ^
* | |
* In the {} brackets is the pattern that -- |
* specifies what to extract from the |
* field as a value to be sent. |
* |
* The string in the field must match the whole pattern --
* before brackets, inside brackets, after brackets.
* When looking at this specific example, we can see that:
* - A key-value pair with the key `table_location`
* and the value matching `instances/&#42;` should be added
* to the x-goog-request-params routing header.
* - The value is extracted from the request message's `table_name` field
* if it matches the full pattern specified:
* `projects/&#42;&#47;instances/&#42;&#47;tables/&#42;`.
* **NB:** If the `path_template` field is not provided, the key name is
* equal to the field name, and the whole field should be sent as a value.
* This makes the pattern for the field and the value functionally equivalent
* to `**`, and the configuration
* {
* field: "table_name"
* }
* is a functionally equivalent shorthand to:
* {
* field: "table_name"
* path_template: "{table_name=**}"
* }
* See Example 1 for more details.
*
* Generated from protobuf field <code>string path_template = 2;</code>
* @param string $var
* @return $this
*/
public function setPathTemplate($var)
{
GPBUtil::checkString($var, True);
$this->path_template = $var;
return $this;
}
}