PHPackages                             manala/manalize - 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. [DevOps & Deployment](/categories/devops)
4. /
5. manala/manalize

AbandonedArchivedLibrary[DevOps & Deployment](/categories/devops)

manala/manalize
===============

Lightweight binary providing vagrant stacks provisionned through manala ansible roles

v0.10.2(6y ago)36642[9 issues](https://github.com/manala/manalize/issues)[1 PRs](https://github.com/manala/manalize/pulls)MITPHPPHP ^7.1.3

Since Sep 20Pushed 5y ago10 watchersCompare

[ Source](https://github.com/manala/manalize)[ Packagist](https://packagist.org/packages/manala/manalize)[ Docs](https://github.com/manala/manalize)[ RSS](/packages/manala-manalize/feed)WikiDiscussions master Synced 2mo ago

READMEChangelog (10)Dependencies (14)Versions (26)Used By (0)

> ⚠️ This repository is unmaintained in favor of using the [Manala binary](https://github.com/manala/manala) along with a [recipe](https://github.com/manala/manala-recipes)

Manalize
========

[](#manalize)

[![Build Status](https://camo.githubusercontent.com/ae704e6613073d88b5513f406ef7f5105583c3239451e9d013a44578bb49aecc/68747470733a2f2f7472617669732d63692e6f72672f6d616e616c612f6d616e616c697a652e7376673f6272616e63683d6d6173746572)](https://travis-ci.org/manala/manalize)

This project provides ready-to-use development environments for various projects (Symfony projects, custom apps, etc.).

At this moment, provided environments are based on Vagrant and provisioned through [Manala ansible roles](http://www.manala.io/).
Some Docker based implementations are planned and should appear really soon.

Why?
----

[](#why)

Because we are too lazy for manually setting up local development environments for each project we have to work on. In short, we need to:

- Be able to work on any new/existing project from any platform in minutes
- Enable/disable support for language, package or any various utility as well
- Keep a local environment consistent across projects (practices, tools)
- Have a local environment as close as possible from the production one
- Destroy/rebuild any environment as needed

What's inside?
--------------

[](#whats-inside)

Manalize is built on the shoulders of the following libs :

- [Composer Semver](https://github.com/composer/semver)
- [Guzzle](https://github.com/guzzle/guzzle)
- The Symfony [Console](https://github.com/symfony/console), [Process](https://github.com/symfony/process), [Filesystem](https://github.com/symfony/filesystem) and [Yaml](https://github.com/symfony/yaml) components

Prerequisites
-------------

[](#prerequisites)

- [PHP](http://php.net) 7.1+
- [Vagrant](https://www.vagrantup.com/) 2.2.1+
- [Vagrant Landrush](https://github.com/vagrant-landrush/landrush) 1.3.0+
- [VirtualBox](https://www.virtualbox.org/) 5.2.22+

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

[](#installation)

#### Using the installer (recommended):

[](#using-the-installer-recommended)

```
curl -LSs https://raw.githubusercontent.com/manala/manalize/master/installer.php | php

```

#### Using composer:

[](#using-composer)

```
composer global require manala/manalize

```

#### Using git:

[](#using-git)

```
git clone git@github.com:manala/manalize
cd manalize
composer install
make build
mv manalize.phar /usr/local/bin/manalize
chmod a+x /usr/local/bin/manalize

```

Usage
-----

[](#usage)

### Checking that your host meets our requirements

[](#checking-that-your-host-meets-our-requirements)

Before using `manalize`, you need to ensure that your host is ready. It can easily be achieved by running the following command:

```
manalize check:requirements
```

A list of requirements and recommendations will be shown, sort as you can install/update packages depending on your need and the current state of your host.

### Setting up your environment

[](#setting-up-your-environment)

Given you have a web project that you clone for the first time and you need to run locally, simply execute the `setup` command:

```
manalize setup
```

[![](res/manalize-setup.gif)](res/manalize-setup.gif)

This command interactively configures the virtual machine for your project.
Some files will be added to your project:

- A `Vagrantfile`
- A `Makefile` including some useful tasks that you'll need to use throughout your project
- An `ansible/` directory containing all the configuration related to the VM provisioning
- Eventually some files specific to the chosen environment

Once this step done, your environment is ready so you can provision your VM using the following command:

```
make setup
```

### Working with your environment

[](#working-with-your-environment)

Once the [`setup`](#setting-up-your-environment) process is finished (it may take a few minutes), your environment is operational and your VM is running. To manage it and work with it, just use the `vagrant` command-line tool as usual:

```
vagrant up|halt|reload|ssh
```

[![](res/manalize-vagrant-ssh.gif)](res/manalize-vagrant-ssh.gif)

### Keeping your environment up-to-date

[](#keeping-your-environment-up-to-date)

Given your project's environment is there and your VM works well, its configuration is sticked to what we provided at the moment you created it.
Since the [manala ansible roles](http://manala.io/) evolve (and the corresponding templates as well), you may want to be aware of the important changes made to in order to update your environment accordingly.

To do so, there are two commands to be aware of: `self-update` and `diff`.

#### self-update

[](#self-update)

```
manalize self-update
```

Running this command updates your `manalize` binary to the latest release, coming with the latest configuration templates. After that, you can safely use the `diff` command as shown below.

#### diff

[](#diff)

The `diff` command allows you to get a patch representing the diff between your current project configuration and the one that your current version of the `manalize` binary would have provided.

Getting the diff:

```
manalize diff --env=""

```

Getting the diff for applying the patch immediately:

```
cd
manalize diff --env="" | git apply

```

Getting the diff for applying the patch later:

```
cd
manalize diff --env="" > manalize.patch
git apply manalize.patch

```

*Note:*

> ⚠️ Be careful when applying the patch, any custom change made to your environment configuration will be erased. To minimize risks, we recommend you to look at the patch before trying to apply it.

### Updating an existing environment without immediatly altering its configuration

[](#updating-an-existing-environment-without-immediatly-altering-its-configuration)

Sometimes, it can be useful to setup the environment without affecting the existing project files nor adding new ones, when migrating a project which already uses Vagrant and/or Ansible for instance.

The following command will only update the `ansible/.manalize` metadata file from what you will configure:

```
manalize setup --no-update ~/my-awesome-app

```

So you can then apply a patch provided by the [diff](#diff) command.

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

[](#contributing)

#### Getting the source code

[](#getting-the-source-code)

```
git clone git@github.com:manala/manalize
```

#### Using the executable

[](#using-the-executable)

```
cd
/bin/manalize
```

#### Running the test suite

[](#running-the-test-suite)

```
cd
make test
```

Troubleshooting
---------------

[](#troubleshooting)

Before all, please [ensure your host satisfies each of our requirements](#checking-that-your-host-meets-our-requirements). Your issue(s) may result from unsupported or buggy versions of packages installed on your machine.

If it doesn't, please consider [opening an issue](https://github.com/manala/manalize/issues/new) on this repository. We use github issues for tracking bugs, feature requests and ensuring support.

License
-------

[](#license)

This project is licensed under MIT.
For the whole copyright, see the [LICENSE](LICENSE) file distributed with this source code.

Author information
------------------

[](#author-information)

Manala ()

###  Health Score

30

—

LowBetter than 64% of packages

Maintenance15

Infrequent updates — may be unmaintained

Popularity20

Limited adoption so far

Community20

Small or concentrated contributor base

Maturity58

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 56.3% 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 ~74 days

Recently: every ~143 days

Total

18

Last Release

2258d ago

PHP version history (3 changes)v0.1.0PHP >=5.6

v0.3.0PHP >=7.0

v0.8.0PHP ^7.1.3

### Community

Maintainers

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

---

Top Contributors

[![chalasr](https://avatars.githubusercontent.com/u/7502063?v=4)](https://github.com/chalasr "chalasr (174 commits)")[![ogizanagi](https://avatars.githubusercontent.com/u/2211145?v=4)](https://github.com/ogizanagi "ogizanagi (109 commits)")[![nervo](https://avatars.githubusercontent.com/u/95935?v=4)](https://github.com/nervo "nervo (10 commits)")[![xavier-rdo](https://avatars.githubusercontent.com/u/1587796?v=4)](https://github.com/xavier-rdo "xavier-rdo (5 commits)")[![benji07](https://avatars.githubusercontent.com/u/166890?v=4)](https://github.com/benji07 "benji07 (4 commits)")[![Kocal](https://avatars.githubusercontent.com/u/2103975?v=4)](https://github.com/Kocal "Kocal (2 commits)")[![maximecolin](https://avatars.githubusercontent.com/u/606766?v=4)](https://github.com/maximecolin "maximecolin (1 commits)")[![greedybro](https://avatars.githubusercontent.com/u/46480794?v=4)](https://github.com/greedybro "greedybro (1 commits)")[![ArnaudBenassy](https://avatars.githubusercontent.com/u/8553679?v=4)](https://github.com/ArnaudBenassy "ArnaudBenassy (1 commits)")[![NicolasDievart](https://avatars.githubusercontent.com/u/4649817?v=4)](https://github.com/NicolasDievart "NicolasDievart (1 commits)")[![voronkovich](https://avatars.githubusercontent.com/u/2299535?v=4)](https://github.com/voronkovich "voronkovich (1 commits)")

---

Tags

ansiblemanala-ansible-rolesvagrantdockervagrantansiblemanala

###  Code Quality

Code StylePHP CS Fixer

### Embed Badge

![Health badge](/badges/manala-manalize/health.svg)

```
[![Health](https://phpackages.com/badges/manala-manalize/health.svg)](https://phpackages.com/packages/manala-manalize)
```

###  Alternatives

[shopware/platform

The Shopware e-commerce core

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

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

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

Drupal is an open source content management platform powering millions of websites and applications.

19462.3M1.3k](/packages/drupal-core)[drupal/core-recommended

Locked core dependencies; require this project INSTEAD OF drupal/core.

6939.5M343](/packages/drupal-core-recommended)[shopware/core

Shopware platform is the core for all Shopware ecommerce products.

595.2M386](/packages/shopware-core)[craftcms/cms

Craft CMS

3.6k3.6M2.6k](/packages/craftcms-cms)

PHPackages © 2026

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