PHPackages lrackwitz/para - 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. [CLI & Console](/categories/cli) 4. / 5. lrackwitz/para ActiveLibrary[CLI & Console](/categories/cli) lrackwitz/para ============== A command-line tool for parallel execution of shell commands in multiple directories. 2.2.3(7y ago)6542GPL-3.0-or-later Since Apr 7Compare [ Source](https://github.com/lrackwitz/para)[ Packagist](https://packagist.org/packages/lrackwitz/para)[ RSS](/packages/lrackwitz-para/feed)WikiDiscussions Synced 2d ago READMEChangelogDependencies (13)Versions (16)Used By (2) Para ==== [](#para) [![Build Status](https://camo.githubusercontent.com/aa893c480349a64cb797296cc65ad487ee38389a37d6df5e4cac809c0ba667fe/68747470733a2f2f7472617669732d63692e6f72672f7261636b626572672f706172612e7376673f6272616e63683d6d6173746572)](https://travis-ci.org/rackberg/para)[![Dependency Status](https://camo.githubusercontent.com/e5d6e9d038d8e3547c3d130f9a2ba640d0fba6d8aea289057ade995c31f0df53/68747470733a2f2f646570656e64656e637963692e636f6d2f6769746875622f7261636b626572672f706172612f6261646765)](https://dependencyci.com/github/rackberg/para)[![Current Version](https://camo.githubusercontent.com/41f640ae8935cc2b708c96a1f68a615211ed865627090b5b96356cb6479a2697/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f72656c656173652d322e322e332d3065353438372e737667)](https://github.com/rackberg/para/releases) A command-line tool for parallel execution of shell commands in multiple directories. How to use it? -------------- [](#how-to-use-it) These instructions will show you how to install `para` on your local machine and how to work with it. ### Prerequisites [](#prerequisites) In order to install `para` the following software is needed: ``` git composer ``` ### Installing [](#installing) To install `para` you can choose one of the following methods. #### Standalone (Recommended) [](#standalone-recommended) This is the easiest way to install `para` on your local machine. Just copy the following command-line and paste it into your terminal to run the automatic install script. ``` curl -L https://raw.githubusercontent.com/lrackwitz/para/master/tools/install.sh | sh ``` #### As composer package [](#as-composer-package) This will install `para` into your global composer vendor folder. ``` composer global require lrackwitz/para ``` #### Manually [](#manually) Follow these instructions if you want to install `para` manually: ``` # Clone the repository git clone https://github.com/rackberg/para --branch # Change to the install directory of para cd # Install the composer managed dependencies composer install # Create a symlink ln -s /bin/para /usr/local/bin/para ``` If `para` has been installed correctly you should get the installed version by entering the following command: ``` para --version ``` ### Configuring [](#configuring) Before you can use `para` you need at least to add the directories you want `para` to manage. This can be done by executing the following command: ``` para add:project [] [--foreground_color=] [--background_color=] ``` Arguments: - The value of the argument `project_name` should be a unique single word to identify the directory you want to add. - The value of the argument `project_path` should be the absolute path of the directory you want to manage. - The value of the optional argument `group_name` should be a unique single word to identify a group of projects. The default value is `default`. #### Example [](#example) ``` para add:project project1 /opt/my_first_project my_group --foreground_color=222 para add:project project2 /Users/user/second_project my_group --foreground_color=104 para add:project project3 /Users/user/third_project my_group --foreground_color=129 para add:project project4 /tmp/my_fourth_project --foreground_color=93 ``` This will result in two groups called `my_group` and `default`. The group `my_group` will contain `project1`, `project2` and `project3`. The group `default` will contain only `project4`. color: To see which color code you can choose execute the script tools/colortable.sh To see the current configuration enter this command: ``` para config ``` ### Executing a command in multiple directories (para projects) at the same time [](#executing-a-command-in-multiple-directories-para-projects-at-the-same-time) The following example shows what you need to do to let para execute a shell command in every project configured for a specific group. Open the para shell for a configured project group. ``` para open:shell [options] [--] ``` #### Example [](#example-1) ``` para open:shell my_group ``` And execute any shell command you like. ``` echo "foo" ``` After pressing enter the shell will output something like this: ``` project1: foo project2: foo project3: foo ``` You can continue entering more shell commands or type `exit` to leave the `para shell`. #### Example [](#example-2) Imagine `project1`, `project2` and `project3` have a `composer.json` file. We changed something in the `composer.json` of `project2` and want to sync the changes to `project1` and `project3`. ``` para sync project2 composer.json project3, project1 ``` ### Showing a log by `para` project [](#showing-a-log-by-para-project) Every command you execute in the interactive `para shell` will be logged. Enter the following command to see which commands you've executed and what the output was. ``` para show:log ``` #### Example [](#example-3) Show the log of `para` project `project2`. ``` para show:log project2 ``` ### Extending the functionality with your own code [](#extending-the-functionality-with-your-own-code) To extend the functionality of `para` with your own code, you simply need to create a new composer package. The `type` in the `composer.json` needs to be `para-plugin`. See the example composer.json file: ``` { "name": "vendor/para-plugin-name", "description": "An example para plugin", "type": "para-plugin", "require-dev": { "lrackwitz/para": "^2.0" } } ``` ### Get a list of available `para plugins` [](#get-a-list-of-available-para-plugins) ``` para plugins:available ``` ### Installing a custom `para` plugin [](#installing-a-custom-para-plugin) ``` para install vendor/para-plugin-name ``` ### Uninstalling a plugin [](#uninstalling-a-plugin) ``` para uninstall vendor/para-plugin-name ``` ### Get a list of installed plugins [](#get-a-list-of-installed-plugins) ``` para installed ``` If everything worked, you can now use the extended functionality of your custom `para` plugin when executing `para` as usual. ### Synchronization of files within `para` projects [](#synchronization-of-files-within-para-projects) In order to be able to synchronize files within `para` projects you need to install the `para-sync` plugin. ``` para install lrackwitz/para-sync ``` The code of the para plugin is here: Contributing ------------ [](#contributing) Please read [CONTRIBUTING.md](CONTRIBUTING.md) for details on the code of conduct, and the process for creating issues or submitting pull requests. Versioning ---------- [](#versioning) This project uses [SemVer](https://semver.org/) for versioning. For the versions available, see the [tags on this repository](https://github.com/rackberg/para/tags). Have a look at the [CHANGELOG.md](CHANGELOG.md). Authors ------- [](#authors) - **Lars Rosenberg** - *Initial work* - [Para](https://github.com/rackberg/para) Credits ------- [](#credits) I want to say thank you to [comm-press GmbH](https://comm-press.de/) for supporting me developing `para`. License ------- [](#license) This project is licensed under the GPL-3.0-or-later License - see the [LICENSE.md](LICENSE.md) file for details. ### Health Score 31 — LowBetter than 66% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity13 Limited adoption so far Community6 Small or concentrated contributor base Maturity71 Established project with proven stability 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 ~35 days Recently: every ~50 days Total 16 Last Release 2836d ago Major Versions 1.6.0 → 2.0.02018-01-22 ### Community Maintainers ![](https://avatars.githubusercontent.com/u/1726033?v=4)[rackberg](/maintainers/Rackberg)[@rackberg](https://github.com/rackberg) ### Code Quality TestsPHPUnit ### Embed Badge ![Health badge](/badges/lrackwitz-para/health.svg) ``` [![Health](https://phpackages.com/badges/lrackwitz-para/health.svg)](https://phpackages.com/packages/lrackwitz-para) ``` ### Alternatives [shopware/core Shopware platform is the core for all Shopware ecommerce products. 585.6M551](/packages/shopware-core)[shopware/platform The Shopware e-commerce core 3.4k1.5M3](/packages/shopware-platform)[laravel/framework The Laravel Framework. 34.8k543.8M19.6k](/packages/laravel-framework)[open-dxp/opendxp Content & Product Management Framework (CMS/PIM) 9421.6k59](/packages/open-dxp-opendxp)[pimcore/pimcore Content & Product Management Framework (CMS/PIM/E-Commerce) 3.8k3.8M497](/packages/pimcore-pimcore)[tempest/framework The PHP framework that gets out of your way. 2.2k34.4k13](/packages/tempest-framework) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)