PHPackages                             dsdobrzynski/druposer - 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. dsdobrzynski/druposer

ActiveProject

dsdobrzynski/druposer
=====================

7.0.0(10y ago)214[1 issues](https://github.com/dsdobrzynski/druposer/issues)PHP

Since Apr 20Pushed 10y ago1 watchersCompare

[ Source](https://github.com/dsdobrzynski/druposer)[ Packagist](https://packagist.org/packages/dsdobrzynski/druposer)[ RSS](/packages/dsdobrzynski-druposer/feed)WikiDiscussions 7.x Synced 1mo ago

READMEChangelogDependencies (33)Versions (3)Used By (0)

Druposer
========

[](#druposer)

This is an example of a starting point for developing a Drupal project using Composer.

You can most easily start your Drupal project with this baseline by using [Composer](getcomposer.org):

```
composer create-projectd dsdobrzynski/druposer your_project_name
```

Running this command will download the latest release of this project to a new directory called `your_project_name` and invoke `composer install` inside it, which will trigger additional scripts to create a working Drupal root in the htdocs subdirectory from the packages downloaded with composer.

We reference a custom composer repository in composer.json [here](composer.json#L6-9). This repository was created by traversing the list of known projects on drupal.org using `drupal/parse-composer`, and has the package metadata for all the valid packages with a Drupal 7 release, including Drupal itself.

We use `derhasi/composer-preserve-paths` to preserve custom Drupal paths, and `composer/installers` to install packages to the correct location.

As you add modules to your project, just update composer.json and run `composer update`. You will also need to pin some versions down as you run across point releases that break other functionality. If you are fastidious with this practice, you will never accidentally install the wrong version of a module if a point release should happen between your testing, and client sign off, and actually deploying changes to production. If you are judicious with your constraints, you will be able to update your contrib without trying to remember known untenable versions and work arounds -- you will just run `composer update`and be done.

This strategy may sound a lot like `drush make`, but it's actually what you would get if you took the good ideas that lead to `drush make`, and then discarded everything else about it, and then discarded those good ideas for better ideas, and then added more good ideas.

See:

- [composer](https://getcomposer.org)
    - [composer install](https://getcomposer.org/doc/03-cli.md#install)
    - [composer update](https://getcomposer.org/doc/03-cli.md#update)
    - [composer create-project](https://getcomposer.org/doc/03-cli.md#create-project)
    - [composer scripts](https://getcomposer.org/doc/articles/scripts.md)
- [drupal/parse-composer](https://packagist.org/packages/drupal/parse-composer)

Project Customization
---------------------

[](#project-customization)

You may want to customize a couple of things about your box first. The scripts are built to take most of the work out of configuration. There are pretty much two things you may want to do:

Getting Started Developing
--------------------------

[](#getting-started-developing)

This framework does not provide a dev environment.

It is also worth noting, if you are working on an existing site, that the default install script allows you to provide a reference database in order to start your development. Simply add a sql file to either of the following:

- `build/ref/drupalproject.sql`
- `build/ref/drupalproject.sql.gz`

Use
---

[](#use)

**IMPORTANT**

This project uses the [drop\_ship]('github.com/promet/drop_ship') module to handle the reusable part of deployment, so everything will get disabled if you don't define dependencies. The `DROPSHIP_SEEDS` environment variable (see directly below) should consist of only the top level project module and environment specific modules.

`DROPSHIP_SEEDS=drupalproject:devel`

The Build and Deployment Scripts
================================

[](#the-build-and-deployment-scripts)

You may have noticed that provisioning the Vagrant box causes `build/install.sh`to be invoked, and that this causes all of our modules to be enabled, giving us a starting schema.

You should note that `build/install.sh` really just installs Drupal and then passes off to `build/update.sh`, which is the reusable and non-destructive script for applying updates in code to a Drupal site with existing content. This is the tool you can use when testing to see if your changes have been persisted in such a way that your collaborators can use them:

```
build/install.sh                                # get a baseline
alias drush="$PWD/vendor/bin/drush -r $PWD/htdocs" # use drush from composer
drush sql-dump > base.sql                       # save your baseline
# ... do a whole bunch of Drupal hacking ...
drush sql-dump > tmp.sql                        # save your intended state
drush -y sql-drop && drush sqlc