PHPackages                             drago-ex/project-installer - 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. drago-ex/project-installer

ActiveLibrary[Utility & Helpers](/categories/utility)

drago-ex/project-installer
==========================

Installation and cleanup tools for Drago projects.

v1.0.0(1w ago)0126↑352.4%2MITPHPPHP >=8.3

Since May 30Pushed 6d agoCompare

[ Source](https://github.com/drago-ex/project-installer)[ Packagist](https://packagist.org/packages/drago-ex/project-installer)[ RSS](/packages/drago-ex-project-installer/feed)WikiDiscussions main Synced 1w ago

READMEChangelogDependencies (1)Versions (2)Used By (2)

Drago Project Tools
===================

[](#drago-project-tools)

Tools for automatic installation and cleanup of project resources from Composer packages.

Features
--------

[](#features)

- **`drago-install`**: Automatically copies or replaces files/directories from vendor packages to your project root.
- **`drago-clean`**: Cleans up redundant resource folders in `vendor/drago-ex` to prevent class duplication or namespace collisions.
- **`drago-setup`**: Collects and runs setup commands provided by installed Drago packages.

Installation
------------

[](#installation)

Add the package to your project:

```
composer require drago-ex/project-tools
```

For component development, add it to `require-dev`:

```
composer require --dev drago-ex/project-tools
```

Configuration
-------------

[](#configuration)

In your package's `composer.json`, define what should be installed:

```
"extra": {
    "drago-project": {
        "install": {
            "copy": {
                "resources/Permission": "app/Core/Permission",
                "resources/assets": "assets/naja"
            },
            "replace-once": true,
            "replace-priority": 100,
            "replace": {
                "resources/config/overrides.neon": "app/config/overrides.neon"
            }
        }
    }
}
```

### Global Options

[](#global-options)

To allow installation from packages with the default type `library`, enable this flag in your **root** `composer.json`:

```
"extra": {
    "drago-project": {
        "allow-library-install": true
    }
}
```

*Note: For security, only packages of type `drago-project-resource` are allowed to install resources by default. Use this flag to enable mirroring for standard libraries.*

### Sections:

[](#sections)

- **`copy`**: Copies files only if they do not already exist in the destination. Safe for initial setup.
- **`replace`**: Always overwrites the destination files. Useful for core updates or shared assets.

### Skipping Packages

[](#skipping-packages)

To skip a specific package during installation, add it to the `packages` map in your **root** `composer.json`:

```
"extra": {
    "drago-project": {
        "packages": {
            "vendor/package-name": {
                "skip": true
            }
        }
    }
}
```

When `skip` is set to `true`, the package is ignored entirely - neither `copy` nor `replace` will run for it.

### Skipping Only Copy or Replace

[](#skipping-only-copy-or-replace)

You can also skip only one install section for a package:

```
"extra": {
    "drago-project": {
        "packages": {
            "vendor/package-name": {
                "skip-copy": true,
                "skip-replace": true
            }
        }
    }
}
```

- **`skip-copy`**: Skips only the package `copy` section.
- **`skip-replace`**: Skips only the package `replace` section.
- **`skip`**: Skips the whole package and has priority over section skips.

This is useful for preset packages where files should be overwritten once during initial project composition, but not overwritten again on later Composer updates.

### Install Once

[](#install-once)

Packages that contain `replace` rules can mark themselves as replace-once:

```
"extra": {
    "drago-project": {
        "install": {
            "replace-once": true,
            "replace": {
                "resources/app": "app",
                "resources/assets": "assets"
            }
        }
    }
}
```

After a successful `replace` run, `drago-install` writes this to the root project `composer.json`:

```
"extra": {
    "drago-project": {
        "packages": {
            "vendor/package-name": {
                "skip-replace": true
            }
        }
    }
}
```

The next run keeps the package installed, but skips its `replace` section. The safer `copy` section can still run unless `skip-copy` or `skip` is also enabled.

`replace-once` is not applied in `--dev` mode.

### Replace Priority

[](#replace-priority)

The installer runs in two phases:

1. All package `copy` sections are processed first.
2. Package `replace` sections are processed afterwards and sorted by priority.

Priority is configured in the package `composer.json`:

```
"extra": {
    "drago-project": {
        "install": {
            "replace-priority": 200
        }
    }
}
```

Lower priority runs earlier, higher priority runs later. This means higher-priority overlays win when multiple packages replace the same file.

Default priority is `100`.

Example:

```
drago-ex/project-backend       priority 100
drago-ex/project-backend-ui    priority 200
netis-cms/project-preset       priority 300

```

In this example, `project-backend-ui` can override backend files, and `netis-cms/project-preset` can override both.

Usage
-----

[](#usage)

### Automation

[](#automation)

Add these scripts to your `composer.json` to automate the process:

```
"scripts": {
    "post-install-cmd": [
        "drago-install",
        "drago-clean"
    ],
    "post-update-cmd": [
        "drago-install",
        "drago-clean"
    ]
}
```

### Manual Execution

[](#manual-execution)

You can also run the commands manually from your terminal:

```
vendor/bin/drago-install
vendor/bin/drago-clean
vendor/bin/drago-setup
```

### Options

[](#options)

- `--verbose` or `-v`: Show detailed file-by-file progress during installation.
- `--dev`: Switches the destination directory to `resources/` in the current working directory. Useful for testing installation logic during package development.

Setup Commands
--------------

[](#setup-commands)

Packages can expose setup commands in `extra.drago-project.commands`. These commands can be used for database migrations, generated permission classes or any other post-installation task.

```
"extra": {
    "drago-project": {
        "commands-priority": 10,
        "commands": {
            "db:migrate-auth": "php vendor/bin/migration db:migrate vendor/drago-ex/project-auth/migrations",
            "create:auth-permission": "php vendor/bin/create-auth-permission"
        }
    }
}
```

Run the setup tool from the project root:

```
vendor/bin/drago-setup
```

Inside Docker, run it as the web user:

```
docker compose exec -u www-data server php vendor/bin/drago-setup
```

### Command Priority

[](#command-priority)

The package-level `commands-priority` value controls the order of setup commands from that package. Lower priority runs earlier. Default priority is `100`.

Commands are sorted in two groups:

1. Commands with labels starting with `db:` run first. Use this prefix for database migrations and other database setup tasks.
2. All other commands run afterwards, for example `create:*`, `generate:*` or `get:*`.

Inside each group, commands are sorted by `commands-priority` first and by command label alphabetically second. This keeps migrations before application setup while still making the console order predictable.

Command values can be plain strings. Object values are also supported for readability. Supported object keys are `run`, `command` and `bin`; `run` is the preferred form.

### Setup Interaction

[](#setup-interaction)

- Select specific tasks by number, for example `1,3`.
- Enter `a` to run all tasks sequentially.
- Enter `q` to quit.

`drago-setup` does not inspect the database or Nette container. It only discovers package commands and executes the selected shell command. Database-specific behavior, such as creating the `migrations` table, belongs to the migration command itself.

How it works
------------

[](#how-it-works)

1. `drago-install` scans all installed packages for the `extra.drago-project.install` configuration.
2. It resolves relative paths against the package root and the current working directory.
3. It skips packages listed under `extra.drago-project.packages` in the root `composer.json` with `"skip": true`.
4. It runs all `copy` sections first.
5. It runs `replace` sections afterwards, sorted by `install.replace-priority`.
6. It can skip only `copy` or `replace` sections with `skip-copy` and `skip-replace`.
7. It respects the `allow-library-install` flag in your root `composer.json` (defaults to `false` for libraries).
8. Packages marked with `install.replace-once` automatically add `skip-replace: true` to the root `composer.json` after a successful replace run.
9. `drago-clean` specifically targets `vendor/drago-ex` and removes `resources` directories to keep your vendor clean after files have been mirrored to your project.
10. `drago-setup` scans installed packages for `extra.drago-project.commands` and runs selected setup commands in priority order.

###  Health Score

45

—

FairBetter than 91% of packages

Maintenance98

Actively maintained with recent releases

Popularity14

Limited adoption so far

Community10

Small or concentrated contributor base

Maturity48

Maturing project, gaining track record

 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

Unknown

Total

1

Last Release

10d ago

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/5998929?v=4)[Zdeněk Papučík](/maintainers/accgit)[@accgit](https://github.com/accgit)

---

Top Contributors

[![accgit](https://avatars.githubusercontent.com/u/5998929?v=4)](https://github.com/accgit "accgit (21 commits)")

### Embed Badge

![Health badge](/badges/drago-ex-project-installer/health.svg)

```
[![Health](https://phpackages.com/badges/drago-ex-project-installer/health.svg)](https://phpackages.com/packages/drago-ex-project-installer)
```

###  Alternatives

[symfony/symfony

The Symfony PHP framework

31.4k86.9M2.2k](/packages/symfony-symfony)[symfony/framework-bundle

Provides a tight integration between Symfony components and the Symfony full-stack framework

3.6k246.0M11.0k](/packages/symfony-framework-bundle)[symfony/security-bundle

Provides a tight integration of the Security component into the Symfony full-stack framework

2.5k181.3M2.2k](/packages/symfony-security-bundle)[symfony/web-profiler-bundle

Provides a development tool that gives detailed information about the execution of any request

2.3k156.8M1.1k](/packages/symfony-web-profiler-bundle)[ocramius/package-versions

Provides efficient querying for installed package versions (no runtime IO)

3.2k74.9M124](/packages/ocramius-package-versions)[pocketmine/pocketmine-mp

A server software for Minecraft: Bedrock Edition written in PHP

3.5k77.4k88](/packages/pocketmine-pocketmine-mp)

PHPackages © 2026

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