PHPackages                             lamosty/bedrock-plugin-control - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. lamosty/bedrock-plugin-control

ActiveWordpress-muplugin[Utility & Helpers](/categories/utility)

lamosty/bedrock-plugin-control
==============================

1.0.0(11y ago)5149PHP

Since Mar 20Pushed 10y ago1 watchersCompare

[ Source](https://github.com/lamosty/bedrock-plugin-control)[ Packagist](https://packagist.org/packages/lamosty/bedrock-plugin-control)[ RSS](/packages/lamosty-bedrock-plugin-control/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependencies (1)Versions (4)Used By (0)

Bedrock plugin control
======================

[](#bedrock-plugin-control)

Are you using some special plugins on your development machine, for example [Query Monitor](https://github.com/johnbillion/query-monitor)?

The problem, as you probably already know, is that these development-related plugins are also deployed to production machine. And we don't need development plugins there.

A partial solution is to include these plugins in the `require-dev` part of `composer.json`. That way, they get installed only locally. However, if you also deploy the database to the production server,they are still activated there.

This **must use** plugin activates or deactivates the development plugins based on the environment. The only requirement is to add a new variable `$BEDROCK_DEV_PLUGINS` into `config/application.php` in your Bedrock-powered web application and add this plugin into the `require` part of the `composer.json`.

Examples
--------

[](#examples)

I usually use Query Monitor, Debug Bar Console, P3 Profiler and Rewrite Rules Inspector on my dev machine. My project's `composer.json` thus looks like this:

```
  "require": {
      "lamosty/bedrock-plugin-control": "~0.1.1"
  },
  "require-dev": {
        "wpackagist-plugin/query-monitor": "dev-trunk",
        "wpackagist-plugin/debug-bar-console": "dev-trunk",
        "wpackagist-plugin/rewrite-rules-inspector": "dev-trunk",
        "wpackagist-plugin/p3-profiler": "dev-trunk"
    }
```

`config/application.php` will then look like this:

```
**
 * Plugins which get force-enabled in development environment.
 * Include them in your composer.json "require-dev" so they get installed only on dev machine.
 *
 * Specify relative path to plugin's main PHP file.
 */

$BEDROCK_DEV_PLUGINS = array(
	'query-monitor/query-monitor.php',
	'debug-bar-console/debug-bar-console.php',
	'p3-profiler/p3-profiler.php',
	'rewrite-rules-inspector/rewrite-rules-inspector.php'
);
```

###  Health Score

30

—

LowBetter than 64% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity15

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity65

Established project with proven stability

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~7 days

Total

3

Last Release

4063d ago

Major Versions

0.1.1 → 1.0.02015-04-03

### Community

Maintainers

![](https://www.gravatar.com/avatar/d1fd54fc67ed4996cb896660deac00d86f2e93a50792f8b899e36522367a50a6?d=identicon)[lamosty](/maintainers/lamosty)

---

Top Contributors

[![lamosty](https://avatars.githubusercontent.com/u/4988512?v=4)](https://github.com/lamosty "lamosty (13 commits)")

### Embed Badge

![Health badge](/badges/lamosty-bedrock-plugin-control/health.svg)

```
[![Health](https://phpackages.com/badges/lamosty-bedrock-plugin-control/health.svg)](https://phpackages.com/packages/lamosty-bedrock-plugin-control)
```

###  Alternatives

[rainlab/blog-plugin

Blog plugin for October CMS

17257.7k](/packages/rainlab-blog-plugin)[rainlab/builder-plugin

Builder plugin for October CMS

17147.2k1](/packages/rainlab-builder-plugin)[pfefferle/wordpress-activitypub

The ActivityPub protocol is a decentralized social networking protocol based upon the ActivityStreams 2.0 data format.

5671.4k1](/packages/pfefferle-wordpress-activitypub)[civicrm/civicrm-drupal-8

Open source constituent relationship management for non-profits, NGOs and advocacy organizations.

18238.1k2](/packages/civicrm-civicrm-drupal-8)[mediawiki/semantic-glossary

A terminology markup extension with a Semantic MediaWiki back-end

1352.4k](/packages/mediawiki-semantic-glossary)[humanmade/lottie-lite

A lightweight Lottie Animations Extension for WordPress

374.3k](/packages/humanmade-lottie-lite)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)