PHPackages                             pagesjaunes/jarvis-ci - 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 &amp; Console](/categories/cli)
4. /
5. pagesjaunes/jarvis-ci

ActiveLibrary[CLI &amp; Console](/categories/cli)

pagesjaunes/jarvis-ci
=====================

Vagrant, VirtualBox, Symfony Application managed PHP development stack: Nginx, PHP-FPM, Varnish.

0.3.29(7y ago)13393MITPHPPHP &gt;=5.4.0

Since Mar 25Pushed 7y ago9 watchersCompare

[ Source](https://github.com/pagesjaunes/jarvis)[ Packagist](https://packagist.org/packages/pagesjaunes/jarvis-ci)[ RSS](/packages/pagesjaunes-jarvis-ci/feed)WikiDiscussions develop Synced 1mo ago

READMEChangelog (1)Dependencies (21)Versions (43)Used By (0)

Jarvis
======

[](#jarvis)

The Ultimate tool to manage php application in virtual machine.

Jarvis is designed to assist you in developping Symfony application, by defining common tasks you run on your remote servers.

Jarvis is meant to be your Swiss Army knife, so it features a modular design with multiple sub-commands to keep the codebase manageable and future-friendly.

What is it?
-----------

[](#what-is-it)

The Jarvis simplifies the developing Symfony Application with vagrant virtual machine.

Out of the box, the application can do many great things:

**composer:**

- composer:self-update
- composer:show

**core:**

- core:container:cache-clear

**editor:**

- editor:config:install

**project:**

- project:assets:build
- project:assets:watch
- project:composer:graph-dependencies
- project:composer:graph-dependencies-pagesjaunes
- project:composer:install
- project:composer:update
- project:composer:validate
- project:config:add
- project:config:show
- project:cs:php
- project:editor:open
- project:git:clone
- project:git:hooks:install
- project:git:log
- project:git:mergetool
- project:git:pre-commit
- project:git:status
- project:git:update
- project:lint:all
- project:lint:php
- project:lint:scss
- project:lint:twig
- project:lint:yaml
- project:php:doc
- project:php:metrics
- project:symfony:cache:clear
- project:symfony:debug:container
- project:symfony:debug:event-dispatcher
- project:symfony:debug:router
- project:symfony:debug:translation
- project:symfony:debug:twig
- project:symfony:monitor:health
- project:tests:all
- project:tests:integration
- project:tests:unit

**vagrant:**

- vagrant:build
- vagrant:provision
- vagrant:restart
- vagrant:ssh
- vagrant:start
- vagrant:status
- vagrant:stop

**vm:**

- vm:php:extension:disable
- vm:php:extension:enable
- vm:service
- vm:service:nginx:restart
- vm:service:php\_fpm:restart
- vm:service:varnish:restart

How do I get started?
---------------------

[](#how-do-i-get-started)

You can use Jarvis in one of three ways:

### As a phar (recommended)

[](#as-a-phar-recommended)

You may download a ready-to-use version of Box as a Phar:

```
$ curl -LSs http://pagesjaunes.github.io/jarvis/installer | php
```

The command will check your PHP settings, warn you of any issues, and the download it to the current directory. From there, you may place it anywhere that will make it easier for you to access (such as /usr/local/bin) and chmod it to 755. You can even rename it to just jarvis to avoid having to type the .phar extension every time.

```
$ jarvis —version
```

Whenever a new version of the application is released, you can simply run the update command to get the latest version:

```
$ jarvis self-update
```

### As a global composer install

[](#as-a-global-composer-install)

This is probably the best way when you have other tools like phpunit and other tools installed in this way:

```
$ composer global require pagesjaunes/jarvis-ci --prefer-dist
```

Make sure to place the **~/.composer/vendor/bin** directory in your PATH so the **jarvis** executable is found when you run the **jarvis** command in your terminal.

### As a composer dependency

[](#as-a-composer-dependency)

You may also install Jarvis as a dependency for your Composer managed project:

```
$ composer require --dev pagesjaunes/jarvis
```

(or)

```
{
    "require-dev": {
        "pagesjaunes/jarvis": "0.1"
    }
}
```

Once you have installed the application, you can run the help command to get detailed information about all of the available commands. This should be your go-to place for information about how to use Jarvis. You may also find additional useful information on the wiki. If you happen to come across any information that could prove to be useful to others, the wiki is open for you to contribute.

```
$ jarvis help
```

Managing a Symfony project
--------------------------

[](#managing-a-symfony-project)

To get started, you may want to check out the example application that is ready to be manage by Jarvis. How your project is structured is entirely up to you. All that Jarvis requires is that you have a file called jarvis.yml at the root of your project directory. You can find a complete and detailed list of configuration settings available by seeing the help information for the build command:

```
$ jarvis help project:add
```

Working Directory
-----------------

[](#working-directory)

If specified option **--working-dir (-d)**, use the given directory as working directory.

Example working directory:

```
$ tree -L 1
.
├── README.md
├── assets
├── bin
├── build
├── config
├── jarvis (facultative for extending)
├── jarvis.yml
├── projects
├── provisioning (facultative)
├── vagrant
├── var
└── vendor
```

Example content file *jarvis.yml*:

```
imports:
    - { resource: jarvis/config/services.xml }

parameters:
    app.name: pj-jarvis

    vagrant_directory: "%working_dir%/vagrant"
    projects_config_file_path: "%working_dir%/config/projects.json"
    local_projects_root_dir: "%working_dir%/projects"

    editor_project_external_folders_config:
        - { name: "bundles", path: "%working_dir%/projects/bundles", follow_symlinks: "false" }
        - { name: "assets_common", path: "%working_dir%/assets/common", follow_symlinks: "false" }

    command.project.enabled: true
    command.editor.enabled: true
    command.project.build.enabled: true
    command.project.cs.enabled: true
    command.project.editor.enabled: true
    command.project.git.enabled: true
    command.project.php.enabled: true
    command.project.composer.enabled: true
    command.project.symfony.enabled: true
    command.project.symfony.assets.enabled: true
    command.project.test.enabled: true
    command.project.lint.enabled: true
    command.vagrant.enabled: true
    command.vm.enabled: true
    command.composer.enabled: true
```

Example content file *config/projects.json*:

```
{
    "projects": {
        {
            "project_name": "symfony-distibution",
            "git_repository_url": "https://github.com/symfony/symfony-standard.git",
            "local_git_repository_dir": "%local_projects_root_dir%/webapps/%project_name%",
            "remote_git_repository_dir": "%remote_projects_root_dir%/webapps/%project_name%",
            "git_target_branch": "master",
            "remote_webapp_dir": "%remote_projects_root_dir%/webapps/%project_name%",
            "local_webapp_dir": "%local_projects_root_dir%/webapps/%project_name%",
            "remote_vendor_dir": "/home/vagrant/projects/%project_name%/vendor",
            "local_vendor_dir": "%local_vendor_root_dir%/%project_name%",
            "remote_symfony_console_path": "%remote_webapp_dir%/app/console",
            "remote_phpunit_configuration_xml_path": "%remote_webapp_dir%/app/phpunit.xml.dist"
        },
        "sylius": {
            "project_name": "sylius",
            "git_repository_url": "https://github.com/Sylius/Sylius.git",
            "local_git_repository_dir": "%local_projects_root_dir%/webapps/%project_name%",
            "remote_git_repository_dir": "%remote_projects_root_dir%/webapps/%project_name%",
            "git_target_branch": "master",
            "remote_webapp_dir": "%remote_projects_root_dir%/webapps/%project_name%",
            "local_webapp_dir": "%local_projects_root_dir%/webapps/%project_name%",
            "remote_vendor_dir": "/home/vagrant/projects/%project_name%/vendor",
            "local_vendor_dir": "%local_vendor_root_dir%/%project_name%",
            "remote_symfony_console_path": "%remote_webapp_dir%/app/console",
            "remote_phpunit_configuration_xml_path": "%remote_webapp_dir%/app/phpunit.xml.dist"
        }
    }
}
```

Alias
-----

[](#alias)

Example:

alias example-jarvis="/usr/local/bin/jarvis --working-dir=/path/to/projects/socle"

Autocompletion
--------------

[](#autocompletion)

Enable auto completion of commands and options in the \*~ / .bashrc\* using the *core:autocomplete* command:

Note that the argument to pass the *core:autocomplete* to specify which alias to enable autocompletion. In addition, the autocompletion is different depending on the working directory used.

```
source $(/usr/local/bin/jarvis core:autocomplete jarvis)
```

or

```
source $(/usr/local/bin/jarvis core:autocomplete --working-dir=/path/to/projects/socle example-jarvis)
```

License
-------

[](#license)

Licenced under the [MIT](http://opensource.org/licenses/MIT) licence. See [here](https://github.com/pagesjaunes/jarvis/blob/develop/LICENSE.md)

Contributing
------------

[](#contributing)

You can contribute in one of three ways:

- File bug reports using the issue tracker.
- Answer questions or fix bugs on the issue tracker.
- Contribute new features or update the wiki.

All pull requests should be made to the develop branch, so they can be tested before being merged into the master branch.

The code contribution process is not very formal. You just need to make sure that you follow the symfony coding guidelines. Any new code contributions must be accompanied by unit tests where applicable.

Builds Statuses
---------------

[](#builds-statuses)

Dev Branch: [![Build Status](https://camo.githubusercontent.com/1c3b55e4416adbf9d8ca824b15a099623057b2e66f14070561b522badc9fcf34/68747470733a2f2f7472617669732d63692e6f72672f70616765736a61756e65732f6a61727669732e706e673f6272616e63683d646576656c6f70)](https://travis-ci.org/pagesjaunes/jarvis)

Master Branch: [![Build Status](https://camo.githubusercontent.com/552239263186b68b92c7b4ab8ec441af989aefb1675c31c75cbc19c1bc8657df/68747470733a2f2f7472617669732d63692e6f72672f70616765736a61756e65732f6a61727669732e706e673f6272616e63683d6d6173746572)](https://travis-ci.org/pagesjaunes/jarvis)

###  Health Score

30

—

LowBetter than 64% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity16

Limited adoption so far

Community15

Small or concentrated contributor base

Maturity60

Established project with proven stability

 Bus Factor1

Top contributor holds 92.9% 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 ~35 days

Recently: every ~119 days

Total

41

Last Release

2665d ago

### Community

Maintainers

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

![](https://www.gravatar.com/avatar/a3562c846051422ebd55849ffad4882ece399472b6538ed2190f49f44e2ece58?d=identicon)[Gilles Gallais](/maintainers/Gilles%20Gallais)

---

Top Contributors

[![tonydub](https://avatars.githubusercontent.com/u/722056?v=4)](https://github.com/tonydub "tonydub (13 commits)")[![MatthieuPresse](https://avatars.githubusercontent.com/u/16778419?v=4)](https://github.com/MatthieuPresse "MatthieuPresse (1 commits)")

---

Tags

phpconsolesymfonyinstallerbootstraper

### Embed Badge

![Health badge](/badges/pagesjaunes-jarvis-ci/health.svg)

```
[![Health](https://phpackages.com/badges/pagesjaunes-jarvis-ci/health.svg)](https://phpackages.com/packages/pagesjaunes-jarvis-ci)
```

###  Alternatives

[shopware/platform

The Shopware e-commerce core

3.3k1.5M3](/packages/shopware-platform)[ec-cube/ec-cube

EC-CUBE EC open platform.

78527.0k1](/packages/ec-cube-ec-cube)[sylius/sylius

E-Commerce platform for PHP, based on Symfony framework.

8.4k5.6M651](/packages/sylius-sylius)[contao/core-bundle

Contao Open Source CMS

1231.6M2.4k](/packages/contao-core-bundle)[prestashop/prestashop

PrestaShop is an Open Source e-commerce platform, committed to providing the best shopping cart experience for both merchants and customers.

9.0k15.4k](/packages/prestashop-prestashop)[shopware/core

Shopware platform is the core for all Shopware ecommerce products.

595.2M386](/packages/shopware-core)

PHPackages © 2026

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