PHPackages luyadev/luya-env-dev - 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. luyadev/luya-env-dev ActiveLuya-core[Utility & Helpers](/categories/utility) luyadev/luya-env-dev ==================== The LUYA DEV ENV repo helps you developing new extension and modules or making pull requests to the luya core repos. 1.0.9(4y ago)3666[1 PRs](https://github.com/luyadev/luya-env-dev/pulls)PHP Since Jan 29Pushed 2y ago2 watchersCompare [ Source](https://github.com/luyadev/luya-env-dev)[ Packagist](https://packagist.org/packages/luyadev/luya-env-dev)[ RSS](/packages/luyadev-luya-env-dev/feed)WikiDiscussions master Synced 2w ago READMEChangelog (10)Dependencies (18)Versions (12)Used By (0) [![LUYA Logo](https://raw.githubusercontent.com/luyadev/luya/master/docs/logo/luya-logo-0.2x.png)](https://raw.githubusercontent.com/luyadev/luya/master/docs/logo/luya-logo-0.2x.png) LUYA Dev Environment ==================== [](#luya-dev-environment) [![LUYA](https://camo.githubusercontent.com/c30b61934591d3a6fcb8718a93fd61bf840c0abd8a8d49aa0fdd4ab99567bdf4/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f506f776572656425323062792d4c5559412d627269676874677265656e2e737667)](https://luya.io)[![Latest Stable Version](https://camo.githubusercontent.com/3aceb035496988877fa4321b6d8dcd4838b94cee5032b94b51f6fe71d7b1a287/68747470733a2f2f706f7365722e707567782e6f72672f6c7579616465762f6c7579612d656e762d6465762f762f737461626c65)](https://packagist.org/packages/luyadev/luya-env-dev)[![Total Downloads](https://camo.githubusercontent.com/9cb233beceec1df09f5d679056b1ec84f0a6f45b1003c09bd042b2afc1845410/68747470733a2f2f706f7365722e707567782e6f72672f6c7579616465762f6c7579612d656e762d6465762f646f776e6c6f616473)](https://packagist.org/packages/luyadev/luya-env-dev)[![Slack Support](https://camo.githubusercontent.com/3574a291a5d77f541be2a9aebff47cf60ed44274b70f9d90bdf6d0d7f4911892/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f536c61636b2d6c7579616465762d79656c6c6f77677265656e2e737667)](https://slack.luya.io/) The LUYA DEV ENV repo helps you developing new extension and modules or making pull requests to the luya core repos. Installation ------------ [](#installation) > **Before installing the env dev project, fork the repos you like to work with.** 1. Clone the luya env dev `git clone https://github.com/luyadev/luya-env-dev.git` 2. Rename `configs/env.php.dist` to `configs/env.php` (`mv configs/env.php.dist configs/env.php` 3. Install composer and init repos `composer install` and afterwards `./vendor/bin/luyadev repo/init` 4. Start the env with docker-compose `docker-compose up` 5. You can now ssh (f.e `docker exec -it luya-env-dev_luya_web_1 /bin/bash`) into the web container and execute the commands `./luya migrate`, `./luya import`, `./luya admin/setup`, `./luya health`. 6. Test your setup and visit `localhost:8080` (Maybe you need to create the `public_html/assets` and `runtime` storage and enable permissions fro them) **We recommend using docker and therefore using `docker-compose up`, because this will also run an unglue server you can compile styles with** Working on CMS and Admin ------------------------ [](#working-on-cms-and-admin) If you need to work on CMS or Admin modules, we recommend the above steps has been done and you are running with `docker-compose up`. 1. Edit the module files in the folder `repos/luya-module-...` 2. Install deps from the module with `composer install` (inside the folder of that module, f.e `repos/luya-module-admin`) (this will install the unglue binary f.e) 3. If you change js or css code run the unglue watch command **in the modules folder**: `./vendor/bin/unglue watch --server=localhost:3000` Update your local luya-env-dev repos ------------------------------------ [](#update-your-local-luya-env-dev-repos) To fetch the upstream for all forked modules from the `repos` folder run: `./vendor/bin/luyadev repo/update` Make sure you push each module after update to get your remote fork even with the upstream. > Its highly recommend to leave the master branch of the modules untouched to ensure that rebasing works properly. **Always create a new branch to work on it.** Changes, collaboration and contribution --------------------------------------- [](#changes-collaboration-and-contribution) For all the FORKED repos (not the read only repos) you can now make changes directly in the `repos/` folder. Assuming you want to make a change in the luya-admin-module which you have forked to your account: 1. Go into the luya-module-admin `cd /repos/luya-module-admin`. 2. Create new branch and commit your changes `git branch my-fix` go into branch `git checkout my-fix`. 3. Make your changes and add them `git add .` and commit `git commit -m 'Added something ...'`. 4. Push branch to your fork `git push origin my-fix`. 5. Create pull request from GitHub. Run Unit Tests for a Repo ------------------------- [](#run-unit-tests-for-a-repo) In order to run your tests for the repo please keep in mind that first of all you have to run `composer install` in the **root of the repo** (e.g. `replos/luya-admin-module`) to install all dependencies afterwards run `./vendor/bin/phpunit tests` in the **root of the repo** to run the tests in the tests-folder. Develop your own module or extension ------------------------------------ [](#develop-your-own-module-or-extension) 1. Clone your repo into the repos folder with `./vendor/bin/luyadev repo/clone USERNAME/REPO_NAME`. 2. Create a `Module.php` file accordingly to the [LUYA guide specifications](https://luya.io/guide/app-module). 3. Adding your module via psr-4 binding to your `composer.json` at the autoload section from **luya-env-dev** root directory. 4. Run `composer dump-autoload` for luya-env-dev. 5. Include your module in `configs/env.php`. > If you would like to use the `@bower` alias inside your own module to include dependencies from `vendor/bower` keep in mind that dependecies need to be installed via composer inside your luya-env-dev root directory. Managing assets and vendors in modules and extensions ----------------------------------------------------- [](#managing-assets-and-vendors-in-modules-and-extensions) Please keep in mind that all modules and extensions are treated as independent projects, so do not forget to run in the **root directory of the module** `composer install` and probably `npm install` in the `/resources` directories of modules to download all needed dependencies. Find more infos --------------- [](#find-more-infos) - [Installation instructions](https://luya.io/guide/install) - [API Documentation](https://luya.io/api) - [Collaboration Guide](https://luya.io/guide/luya-collaboration) - [Issues on GitHub](https://github.com/luyadev/luya/issues) ### Health Score 33 — LowBetter than 72% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity15 Limited adoption so far Community17 Small or concentrated contributor base Maturity70 Established project with proven stability Bus Factor1 Top contributor holds 80.4% 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 ~156 days Recently: every ~170 days Total 10 Last Release 1663d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/86184bf08843ed8fcc4aedb2fdecd8a9e832e47e89a7166cebfda529c176f5ce?d=identicon)[nadar](/maintainers/nadar) --- Top Contributors [![nadar](https://avatars.githubusercontent.com/u/3417221?v=4)](https://github.com/nadar "nadar (111 commits)")[![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4)](https://github.com/dependabot[bot] "dependabot[bot] (10 commits)")[![dev7ch](https://avatars.githubusercontent.com/u/15183757?v=4)](https://github.com/dev7ch "dev7ch (9 commits)")[![TheMaaarc](https://avatars.githubusercontent.com/u/3450438?v=4)](https://github.com/TheMaaarc "TheMaaarc (6 commits)")[![hbugdoll](https://avatars.githubusercontent.com/u/6715827?v=4)](https://github.com/hbugdoll "hbugdoll (1 commits)")[![slowfox089](https://avatars.githubusercontent.com/u/10498253?v=4)](https://github.com/slowfox089 "slowfox089 (1 commits)") --- Tags collaborationcomposerdevelopmentdevelopment-toolsextensionhacktoberfestluyamodulephpbuilderextensionmoduledeveloperluya ### Embed Badge ![Health badge](/badges/luyadev-luya-env-dev/health.svg) ``` [![Health](https://phpackages.com/badges/luyadev-luya-env-dev/health.svg)](https://phpackages.com/packages/luyadev-luya-env-dev) ``` ### Alternatives [leantime/leantime Open source project management system for non-project managers. Simple like Trello, powerful like Jira. Built with neurodiversity in mind. 10.1k3.4k](/packages/leantime-leantime)[luyadev/luya-module-payment LUYA Payment allows you to integrate payments in a safe and fast way. The module take care of all the provider required steps (call, create, success, abort, etc.) and provides all the informations for your store. 1012.2k](/packages/luyadev-luya-module-payment)[opengento/composer-registration-plugin This plugin allows to compile the Magento2 components registrations on composer install/update. 101.7k](/packages/opengento-composer-registration-plugin) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)