20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

This argument is valid only in combination with `local` role parameter, and it
is not being called in this combination anymore.

20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

It makes sense (and even possible at all) to controll Docker containers from
local environment. Replacing `fab_run()` directly with `local()` calls ensures
that container management will not be performed inside of Docker instance or on
remote server because of a configuration error.

20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

The `fab_run()` function does not add any behavior for local calls, only
ambiguity of the command execution environment.

Inlining `local()` calls contributes to a clear separation of enrivonments.

Regularize usage of locale and site_languages config

On n'a pas de besoin d'avoir deux parameters qui configure la locale d'installation. Seulement site_languages is suffisant.

See merge request !23

20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

The `site_languages` parameter can receive multiple language codes separated by
commas. Thus its value cannot be reused as-is as a value of `locale` parameter
which is passed to Drush during site installation.

The value of `site_languages` must be split, and the first element in the list
of languages will be used as a site locale during installation.

20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

Locale configuration during installation is done with two config parameters:
`locale` and `site_languages`, which is excessive. Given that the `locale`
parameter is a simple boolean, its value can be inferred from the value of
`site_languages` parameter.

20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

Do not try to download translation if no languages were set in site
configuration. Otherwise, Drush will try to download translations, will be able
to find anything, and ultimately fail environment initialization.

Do not update /etc/hosts file if target hostname is not set



See merge request !21

Change default vars values to something that does not crash Drupalizer



See merge request !20

20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

It is better to use the most common IP address assigned to Docker containers
than to use a network broadcast address.

20th (Victor Nikulshin) authored Nov 02, 2016 and Victor Nikulshin committed Nov 07, 2016

If configured host name is empty, Drupalizer will construct an invalid `sed`
invocation to modify `/etc/hosts` file. As the result, environment
initialization will fail.

Reformat code to match Python coding standards



See merge request !17

Exposing tasks from deploy module by their old names in addition to namespaced
names for backwards compatibility.

Adding and removing blank lines where appropriate to be more in accordance with
Python coding standards.

If function 'deploy' is defined in __init__.py it masks the imported module
with the same name. Placing it into deploy.py file is more logical
structure-wise.

To make sure that the command is still accessible by its old name, it is marked
as a default task for 'deploy' module.

Change drush.aliases execution context from local to DOCKER

This resolves right issues that I've seen happening under
certain circumstances.

See merge request !19

This resolves right issues that I've seen happening under
certain circumstances.

Use docker executor to run health check and sonar

Fix the `.gitlab-ci.yml` to properly run a simple health check, and a [SonarQube](http://sonarqube.org/) static analysis.


The SonarQube instance runs at https://sonarqube.savoirfairelinux.net/. Credentials to login are available in SFLvault (m#2222)

See merge request !18

Feature/file system rights



See merge request !16

Check if env.site_profile is a core profile

I had errors with drush8 when not specifying a profile on site-install

See merge request !14

Add parent directory creation when creating drush aliases' directory

<sites/all/> might not have been created yet (in drush8+d8 for instance)

See merge request !15

<sites/all/> might not have been created yet.

Enable GitLab CI

* Provide a .gitlab-ci.yml

See merge request !11

Revert "Merge branch 'feature/update-doc' into '2.x'"

This reverts merge request !9

See merge request !10

Add fab --list command as health check

Add a basic config file to analyse code with sonar

Lookup http://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner#AnalyzingwithSonarQubeScanner-Installation in order to install and configure sonar-scanner on your development box.

See merge request !8

This reverts merge request !9