Commit bd371f60 authored by pierre ozoux's avatar pierre ozoux


parent ef200520
# About this project
The goal of this project is to provide a Web UI to manage users and organisations in a convivial marketplace and management for free/indie/librehosting.
The goal of this project is to provide a WebUI to manage users, groups, organisations and there related services in a convivial marketplace.
The project is built on Drupal 8, with a strong emphasis on commerce and LDAP integration.
Think of it as Google apps for business but with the freedom to add any applications to your organisations, and choose to host them on premises or in the cloud!
# Status
# Composer template for Drupal projects
This is currently the design phase.
[![Build Status](](
For more information:
This project template should provide a kickstart for managing your site
dependencies with [Composer](
If you want to know how to use it as replacement for
[Drush Make]( visit
the [Documentation on](
## Usage
First you need to [install composer](
> Note: The instructions below refer to the [global composer installation](
You might need to replace `composer` with `php composer.phar` (or similar)
for your setup.
After that you can create the project:
composer create-project drupal-composer/drupal-project:8.x-dev some-dir --stability dev --no-interaction
With `composer require ...` you can download new dependencies to your
cd some-dir
composer require drupal/devel:8.*
The `composer create-project` command passes ownership of all files to the
project that is created. You should create a new git repository, and commit
all files not excluded by the .gitignore file.
## What does the template do?
When installing the given `composer.json` some tasks are taken care of:
* Drupal will be installed in the `web`-directory.
* Autoloader is implemented to use the generated composer autoloader in `vendor/autoload.php`,
instead of the one provided by Drupal (`web/vendor/autoload.php`).
* Modules (packages of type `drupal-module`) will be placed in `web/modules/contrib/`
* Theme (packages of type `drupal-theme`) will be placed in `web/themes/contrib/`
* Profiles (packages of type `drupal-profile`) will be placed in `web/profiles/contrib/`
* Creates default writable versions of `settings.php` and `services.yml`.
* Creates `sites/default/files`-directory.
* Latest version of drush is installed locally for use at `vendor/bin/drush`.
* Latest version of DrupalConsole is installed locally for use at `vendor/bin/drupal`.
## Updating Drupal Core
This project will attempt to keep all of your Drupal Core files up-to-date; the
project [drupal-composer/drupal-scaffold](
is used to ensure that your scaffold files are updated every time drupal/core is
updated. If you customize any of the "scaffolding" files (commonly .htaccess),
you may need to merge conflicts if any of your modfied files are updated in a
new release of Drupal core.
Follow the steps below to update your core files.
1. Run `composer update drupal/core --with-dependencies` to update Drupal Core and its dependencies.
1. Run `git diff` to determine if any of the scaffolding files have changed.
Review the files for any changes and restore any customizations to
`.htaccess` or `robots.txt`.
1. Commit everything all together in a single commit, so `web` will remain in
sync with the `core` when checking out branches or running `git bisect`.
1. In the event that there are non-trivial conflicts in step 2, you may wish
to perform these steps on a branch, and use `git merge` to combine the
updated core files with your customized files. This facilitates the use
of a [three-way merge tool such as kdiff3]( This setup is not necessary if your changes are simple;
keeping all of your modifications at the beginning or end of the file is a
good strategy to keep merges easy.
## Generate composer.json from existing project
With using [the "Composer Generate" drush extension](
you can now generate a basic `composer.json` file from an existing project. Note
that the generated `composer.json` might differ from this project's file.
## FAQ
### Should I commit the contrib modules I download
Composer recommends **no**. They provide [argumentation against but also
workrounds if a project decides to do it anyway](
### How can I apply patches to downloaded modules?
If you need to apply patches (depending on the project being modified, a pull
request is often a better solution), you can do so with the
[composer-patches]( plugin.
To add a patch to drupal module foobar insert the patches section in the extra
section of composer.json:
"extra": {
"patches": {
"drupal/foobar": {
"Patch description": "URL to patch"
To get notified about incoming features and keep in touch with the community:
\ No newline at end of file
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment