bromate

Bromate Remote Media Bridge helps WordPress installations share the same database across multiple environments without requiring a full copy of the uploads directory.
Instead of synchronizing gigabytes of media files between environments, the plugin allows WordPress to use a remote uploads directory while keeping the local media library structure intact.
The plugin can:
<ul>
<li>Rewrite attachment URLs generated by WordPress.</li>
<li>Rewrite responsive image URLs in srcset attributes.</li>
<li>Redirect media requests to a remote uploads directory.</li>
<li>Progressively cache remote media files locally while visitors browse your site.</li>
<li>Reduce deployment complexity for large media libraries.</li>
</ul>
This is particularly useful for:
<ul>
<li>Local development environments using a production database.</li>
<li>Staging and pre-production environments.</li>
<li>WordPress redesign and migration projects.</li>
<li>Large sites where synchronizing the entire uploads directory is impractical.</li>
<li>Long-running projects where the production media library changes frequently.</li>
</ul>
<h3>Example</h3>
A local site generates:
<pre><code>https://local.example.test/wp-content/uploads/2026/05/image.jpg
</code></pre>
Bromate Remote Media Bridge rewrites it to:
<pre><code>https://production.example.com/wp-content/uploads/2026/05/image.jpg
</code></pre>
When “Download while navigating” is enabled, the file may also be downloaded automatically and stored locally the first time it is requested.
This creates a progressively warmed local media cache containing only the files that have actually been viewed.
<h3>Features</h3>
<ul>
<li>Rewrite WordPress attachment URLs.</li>
<li>Rewrite responsive image URLs (srcset).</li>
<li>Redirect direct media requests.</li>
<li>Progressive local media caching while browsing.</li>
<li>Automatic local storage of viewed remote media files.</li>
<li>Excluded URL support.</li>
<li>Environment-specific configuration through constants.</li>
<li>Optional debug logging.</li>
<li>No custom database tables.</li>
<li>No front-end assets.</li>
<li>Works with shared databases across development, staging and production environments.</li>
</ul>
<h3>Configuration</h3>
The remote uploads URL should point directly to the uploads directory of the environment containing the media files.
Example:
<pre><code>https://www.example.com/wp-content/uploads
</code></pre>
You may also configure the plugin using constants in wp-config.php:
<pre><code>define( 'BROMATE_REMOTE_MEDIA_BRIDGE_ENABLED', true );

define( 'BROMATE_REMOTE_MEDIA_BRIDGE_BASE_URL', 'https://www.example.com/wp-content/uploads' );

define( 'BROMATE_REMOTE_MEDIA_BRIDGE_DOWNLOAD_WHILE_NAVIGATING', true );

define( 'BROMATE_REMOTE_MEDIA_BRIDGE_DEBUG', false );
</code></pre>
Constants take precedence over saved settings.

Bromate Remote Media Bridge

Use a remote WordPress uploads directory without copying your entire media library. Optionally cache media files locally as visitors browse your site.

Scott Reilly

Though it is typically an individually configurable aspect of WordPress, there are times when forcing a single admin color scheme upon all users of a site can be warranted, such as to:
<ul>
<li>Provide a unique backend color scheme for multiple sites used by the same set of users to reinforce the difference between the sites.</li>
<li>Clearly denote backend differences between a production and staging/test instance of a site. Especially given that in this situation with the same plugins active and often the same data present, it can be easy to get mixed up about what site you’re actually on.</li>
<li>Force a site brand-appropriate color scheme.</li>
<li>Crush the expression of individuality under your iron fist.</li>
</ul>
Additionally, the plugin removes the “Admin Color Scheme” profile setting from users who don’t have the capability to set the admin color scheme globally since being able to set its value gives them the false impression that it may actually apply.
Links: <a href="https://coffee2code.com/wp-plugins/force-admin-color-scheme/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/force-admin-color-scheme/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/force-admin-color-scheme/" rel="nofollow ugc">GitHub</a> | <a href="https://coffee2code.com" rel="nofollow ugc">Author Homepage</a>
<h3>Hooks</h3>
The plugin is further customizable via one filter. Typically, code making use of filters should ideally be put into a mu-plugin or site-specific plugin (which is beyond the scope of this readme to explain).
c2c_force_admin_color_scheme (filter)
The ‘c2c_force_admin_color_scheme’ filter allows you to set or override the forced admin color scheme. Use of the constant (“) takes priority over the filtered value, but the filtered value takes priority over the value set via the admin.
Arguments:
<ul>
<li>$color (string): The name of the admin color scheme. If an empty string is returned, then the plugin will behave as if no forced admin color scheme has been defined.</li>
</ul>
Example:
<pre><code>/**
 * Sets a forced admin color scheme based on user. Admins get one color scheme, whereas everyone else gets another.
 *
 * @param string $color The current forced admin color scheme. Empty string indicates no forced admin color scheme.
 * @return string
 */
function my_c2c_force_admin_color_scheme( $color ) {
 return current_user_can( 'manage_options' ) ? 'sunrise' : 'coffee';
}
add_filter( 'c2c_force_admin_color_scheme', 'my_c2c_force_admin_color_scheme' );
</code></pre>

Force Admin Color Scheme

Force a single admin color scheme for all users of the site.

Bromate Remote Media Bridge vs Force Admin Color Scheme