Adds drupal-composer, untested

12 files changed, 1695 insertions, 0 deletions

diff --git a/share/templater/drupal-composer/description b/share/templater/drupal-composer/description
new file mode 100644
index 0000000..3c1510c
--- /dev/null
+++ b/share/templater/drupal-composer/description
@@ -0,0 +1 @@
+Drupal project using Composer
diff --git a/share/templater/drupal-composer/files/Makefile.drupal-composer b/share/templater/drupal-composer/files/Makefile.drupal-composer
new file mode 100644
index 0000000..c8f26ec
--- /dev/null
+++ b/share/templater/drupal-composer/files/Makefile.drupal-composer
@@ -0,0 +1,324 @@
+#
+# Makefile for a Drupal 8 Application using Composer - https://templater.fluxo.info
+#
+
+# Parameters
+PROJECT      = drupal
+DATABASE     = $(PROJECT)
+SITES_FOLDER = web/sites
+SITE_FOLDER  = $(SITES_FOLDER)/default
+DRUSH        = drush
+DATE         = $(shell date +%Y%m%d)
+
+# Setup production environment
+production: post_receive composer settings perms
+
+# Setup virtual machine using kvmx
+kvmx:
+	#kvmx up || true
+	kvmx provision
+	#echo '( cd /srv/shared && make drush   )'  | kvmx ssh
+	#echo '( cd /srv/shared && make vendor  )'  | kvmx ssh
+	echo '( cd /srv/shared && make production)' | kvmx ssh
+	#kvmx ssh "$(DRUSH) pm-enable devel -y"
+
+# Run composer
+composer:
+	composer install
+	@#composer update
+	composer dump-autoload --optimize --profile
+
+# Drupal settings
+settings:
+	test -s   $(SITES_FOLDER)/sites.php         || cp $(SITES_FOLDER)/example.sites.php            $(SITES_FOLDER)/sites.php
+	test -s   $(SITE_FOLDER)/settings.php       || cp $(SITE_FOLDER)/../example.settings.php       $(SITE_FOLDER)/settings.php
+	test -s   $(SITE_FOLDER)/settings.local.php || cp $(SITE_FOLDER)/../example.settings.local.php $(SITE_FOLDER)/settings.local.php
+	chmod 640 $(SITE_FOLDER)/settings.local.php
+	chmod 640 $(SITE_FOLDER)/services.yml
+
+# Permissions
+perms:
+	chmod 755 cli
+	chmod 755 web/sites/default
+	chmod 755 web/sites/default/files
+
+# Reset the working copy
+reset:
+	@#git reset HEAD
+	git checkout -f
+
+# Deploy code pushed on remote host
+deploy: perms reset
+	composer install
+	$(DRUSH) updatedb
+	$(DRUSH) cache-rebuild
+	$(DRUSH) config-import -y
+
+# Load pristine db from the initial upstream developer
+initdb_pristine: settings
+	test -s sql/dumps/pristine.zip && unzip -p sql/dumps/pristine.zip | $(DRUSH) sql-cli || true
+	test -s sql/dumps/pristine.zip && $(DRUSH) updatedb -y || true
+
+# Load the database dump, clear the drupal cache and updated database
+# See https://www.drupal.org/node/628130
+initdb: settings
+	test -s sql/dumps/latest.sql.gz && gzip -dc sql/dumps/latest.sql.gz | $(DRUSH) sql-cli || true
+	test -s sql/dumps/latest.sql.gz && $(DRUSH) updatedb -y || true
+
+# Dump the database, clearing the cache to ensure a small package
+dumpdb: settings cache
+	mkdir -p sql/dumps
+	rm -f sql/dumps/latest.sql.gz
+	rm -f sql/dumps/$(DATE).sql.gz
+	$(DRUSH) sql-dump > sql/dumps/$(DATE).sql
+	( cd sql/dumps && gzip $(DATE).sql && ln -s $(DATE).sql.gz latest.sql.gz )
+
+# Destroy the database
+destroydb: settings
+	echo "DROP DATABASE $(DATABASE); CREATE DATABASE $(DATABASE);" | $(DRUSH) sql-cli
+
+# Reinitializes the database
+reinitdb: destroydb initdb
+
+# Clear drupal cache
+cache:
+	$(DRUSH) cache-rebuild
+
+# Export configuration
+export:
+	$(DRUSH) config-export -y
+
+# Import configuration
+import:
+	$(DRUSH) config-import -y
+
+sync_files_from_development:
+	rsync -avz --delete $(DEVELOPMENT)/sql/dumps/ sql/dumps/
+	rsync -avz --delete $(DEVELOPMENT)/$(SITE_FOLDER)/files/ $(SITE_FOLDER)/files/
+
+sync_files_from_production:
+	rsync -avz --delete $(PRODUCTION)/sql/dumps/ sql/dumps/
+	rsync -avz --delete $(PRODUCTION)/$(SITE_FOLDER)/files/ $(SITE_FOLDER)/files/
+
+sync_files_to_development:
+	rsync -avz --delete sql/dumps/ $(DEVELOPMENT)/sql/dumps/
+	rsync -avz --delete $(SITE_FOLDER)/files/ $(DEVELOPMENT)/$(SITE_FOLDER)/files/
+
+sync_files_to_production:
+	rsync -avz --delete sql/dumps/ $(PRODUCTION)/sql/dumps/
+	rsync -avz --delete $(SITE_FOLDER)/files/ $(PRODUCTION)/$(SITE_FOLDER)/files/
+
+updatedb:
+	$(DRUSH) updatedb -y
+
+composer_update:
+	composer update drupal/core --with-dependencies
+
+# Upgrade drupal
+upgrade-drupal: composer_update updatedb
+
+# Parameters
+CORE      = 8
+PROJECT   = drupal
+DATABASE ?= $(PROJECT)
+ENV      ?= dev
+DATE      = $(shell date +%Y%m%d)
+CWD       = $(shell pwd)
+DESTDIR  ?= /var/www/data
+DRUPAL    = $(DESTDIR)/drupal-$(CORE)
+DRUSH     = drush -r $(DRUPAL) -l $(PROJECT)
+
+# Setup production environment
+production: submodules post_receive drush settings ownership
+
+# Setup a development environment
+develop: submodules $(CONTAINER)
+	#rm -rf $(DRUPAL)/sites/default
+	#ln -s $(PROJECT) $(DRUPAL)/sites/default
+
+# Old target
+# Install the platform
+#platform: drupal drush settings symlinks initdb cache
+
+# Keep code in sync
+sync-code: update drush cache import
+
+# Initialize and update git submodules
+submodules:
+	git submodule sync          --recursive
+	git submodule update --init --recursive
+
+# Setup the virtual machine using vagrant
+vagrant:
+	vagrant up || true
+	vagrant provision
+	echo '( cd /vagrant && make drush )'    | vagrant ssh
+	echo '( cd /vagrant && make settings )' | vagrant ssh
+	#vagrant ssh -c "$(DRUSH) pm-enable devel -y"
+
+# Setup the virtual machine using kvmx
+kvmx:
+	#kvmx up || true
+	kvmx provision
+	echo '( cd /srv/shared && make drush )'    | kvmx ssh
+	echo '( cd /srv/shared && make settings )' | kvmx ssh
+	#kvmx ssh "$(DRUSH) pm-enable devel -y"
+
+# Old target
+# Download drupal, setup folder structure and config file
+#
+# You might want to use "-n" to avoid _drush_recursive_copy cpu hog if previous
+# installation already exists when using 9p filesystem
+#drupal:
+#	#rm -rf $(DESTDIR)/drupal-$(CORE)* && drush pm-download -y -v drupal-$(CORE) --destination=/tmp/drupal && mv /tmp/drupal/drupal-$(CORE).* $(DESTDIR)/
+#	#drush pm-download -y -v drupal-$(CORE) --destination=$(DESTDIR)
+#	#( cd $(DRUPAL)/.. && ln -s drupal-$(CORE).* drupal-$(CORE) )
+#	BASE=$(DESTDIR) drupal download $(CORE)
+
+# Old target
+# Make the needed symlinks
+#symlinks:
+#	ln -sf -t $(DRUPAL)/sites/$(PROJECT)/ $(CWD)/files
+#	ln -sf -t $(DRUPAL)/sites/$(PROJECT)/ $(CWD)/config
+#	ln -sf -t $(DRUPAL)/sites/$(PROJECT)/ $(CWD)/themes
+#	ln -sf -t $(DRUPAL)/sites/$(PROJECT)/ $(CWD)/modules
+#	ln -sf -t $(DRUPAL)/sites/$(PROJECT)/ $(CWD)/libraries
+
+# Default settings
+default_settings:
+	test -s sites.php        || cp $(DRUPAL)/sites/example.sites.php            sites.php
+	test -s settings.dev.php || cp $(DRUPAL)/sites/default/default.settings.php settings.dev.php
+	test -s services.dev.yml || cp $(DRUPAL)/sites/default/default.services.yml services.dev.yml
+
+# Custom settings
+custom_settings:
+	#test -s   $(DRUPAL)/sites/sites.php                      || cp sites.php              $(DRUPAL)/sites/sites.php
+	#mkdir -p  $(DRUPAL)/sites/$(PROJECT)
+	#test -s   $(DRUPAL)/sites/$(PROJECT)/settings.$(ENV).php || cp settings.dev.php       $(DRUPAL)/sites/$(PROJECT)/settings.$(ENV).php
+	#test -s   $(DRUPAL)/sites/$(PROJECT)/settings.php        || ln -s settings.$(ENV).php $(DRUPAL)/sites/$(PROJECT)/settings.php
+	#test -s   $(DRUPAL)/sites/$(PROJECT)/services.$(ENV).yml || cp services.dev.yml       $(DRUPAL)/sites/$(PROJECT)/services.$(ENV).yml
+	#test -s   $(DRUPAL)/sites/$(PROJECT)/services.yml        || ln -s services.$(ENV).yml $(DRUPAL)/sites/$(PROJECT)/services.yml
+	#chmod 640 $(DRUPAL)/sites/$(PROJECT)/settings.php
+	#chmod 640 $(DRUPAL)/sites/$(PROJECT)/services.yml
+	test -s   settings.$(ENV).php || cp settings.dev.php       settings.$(ENV).php
+	test -s   settings.php        || ln -s settings.$(ENV).php settings.php
+	test -s   services.$(ENV).yml || cp services.dev.yml       services.$(ENV).yml
+	test -s   services.yml        || ln -s services.$(ENV).yml services.yml
+	chmod 640 settings.php
+	chmod 640 services.yml
+
+# Setup drupal settings
+settings: default_settings custom_settings
+	test -s $(DRUPAL)/sites/sites.php || sudo cp sites.php $(DRUPAL)/sites/sites.php
+
+# Fix ownership
+ownership:
+	sudo chown -R $(PROJECT). $(DRUPAL)/sites/$(PROJECT)
+	sudo chmod 755            $(DRUPAL)/sites/$(PROJECT)
+
+# Run drush makefile
+drush:
+	sudo drush make -n --no-core drupal.make.yml $(DRUPAL)
+
+# Run drush site-install
+site_install: settings
+	$(DRUSH) site-install -y
+
+# Run drush site-install, sqlite version
+# See https://api.drupal.org/api/drupal/core%21INSTALL.sqlite.txt/8.4.x
+site_install_sqlite: settings
+	mkdir -p sql/.ht.sqlite
+	touch sql/dumps/.ht.sqlite
+	$(DRUSH) site-install --db-url=sqlite://$(CWD)/sql/dumps/.ht.sqlite
+
+# Update the database
+updatedb:
+	$(DRUSH) updatedb -y --entity-updates
+
+# Load the database dump, clear the drupal cache and fix image paths
+# See https://www.drupal.org/node/628130
+initdb: settings
+	test -s sql/dumps/latest.sql.gz && gzip -dc sql/dumps/latest.sql.gz | $(DRUSH) sql-cli || true
+	test -s sql/dumps/latest.sql.gz && $(DRUSH) updatedb -y || true
+
+# Dump the database, clearing the cache to ensure a small package
+dumpdb: settings cache
+	mkdir -p sql/dumps
+	rm -f sql/dumps/latest.sql.gz
+	rm -f sql/dumps/$(DATE).sql.gz
+	$(DRUSH) sql-dump > sql/dumps/$(DATE).sql
+	( cd sql/dumps && gzip $(DATE).sql && ln -s $(DATE).sql.gz latest.sql.gz )
+
+# Clear drupal cache
+cache:
+	$(DRUSH) cache-rebuild
+
+# Destroy the database
+destroydb: settings
+	echo "DROP DATABASE $(DATABASE); CREATE DATABASE $(DATABASE);" | $(DRUSH) sql-cli
+
+# Reinitializes the database
+reinitdb: destroydb initdb
+
+# Cleanup develop environment
+clean:
+	vagrant halt 			 || true
+	vagrant destroy -f || true
+	kvmx stop 				 || true
+	kvmx destroy 			 || true
+	rm -rf vendor/drupal*
+
+# Export configuration
+export:
+	$(DRUSH) config-export -y
+
+# Import configuration
+import:
+	$(DRUSH) config-import -y
+
+# Diff configuration
+# Needs https://github.com/eriktufvesson/drush-config-diff
+diff:
+	$(DRUSH) config-diff
+
+# Update the codebase
+update: pull submodules
+
+# Upgrade modules
+upgrade-modules:
+	sudo $(DRUSH) up
+
+# Upgrade drupal
+upgrade-drupal:
+	BASE=$(DESTDIR) sudo drupal upgrade $(CORE)
+
+# Configure update hook on remote host
+#post_receive:
+#	git config receive.denyCurrentBranch ignore
+#	cd .git/hooks && ln -sf ../../bin/post-receive
+
+# Pull changes
+pull:
+	git pull
+
+# Reset the working copy
+reset:
+	#git reset HEAD
+	git checkout -f
+
+# Fix local folder permission
+perms:
+	chmod 755 .
+
+# Deploy code pushed on remote host
+deploy: perms reset submodules
+	drush cache-rebuild
+	drush config-import -y
+
+sync_files_from_development:
+	rsync -avz --delete $(DEVELOPMENT)/sql/dumps/ sql/dumps/
+	rsync -avz --delete $(DEVELOPMENT)/files/     files/
+
+sync_files_from_production:
+	rsync -avz --delete $(PRODUCTION)/sql/dumps/ sql/dumps/
+	rsync -avz --delete $(PRODUCTION)/files/     files/
diff --git a/share/templater/drupal-composer/files/README.drupal-composer.md b/share/templater/drupal-composer/files/README.drupal-composer.md
new file mode 100644
index 0000000..46069f3
--- /dev/null
+++ b/share/templater/drupal-composer/files/README.drupal-composer.md
@@ -0,0 +1,81 @@
+Drupal 8 Application HOWTO
+==========================
+
+This is the basic worflow for a Drupal 8 project set using
+[templater](https://templater.fluxo.info).
+
+Requirements
+------------
+
+Basique requirements are:
+
+* A [make](https://packages.debian.org/stable/make) implementation.
+* Container manager like vagrant, docker or [kvmx](https://kvmx.fluxo.info).
+
+Copying files
+-------------
+
+Put files and database dumps in the following folders:
+
+    rsync -avz --delete /path/to/backups/files/ files/
+    rsync -avz --delete /path/to/backups/sql/   sql/
+
+Check the Makefile.drupal8 for the db dump file name and format. Commands like
+the examples above can be used to transport files from production back to the
+development trees.
+
+Development
+-----------
+
+Create the development environment using
+
+    make develop
+
+You might need to setup vagrant, docker or kvmx first.
+
+## Default site installation
+
+If you need a fresh drupal database installation, do this in the project
+folder inside the container:
+
+    make site_install
+
+## Loading and reloading the database
+
+To load or reload the database from the latest dump available at the `sql/`
+folder, do the following in the project folder and inside the container:
+
+    make reinitdb
+
+## Acessing
+
+The exact port dependes on what you configured on your container configuration,
+but you should be able to reach your drupal installation at an address like
+
+    http://localhost:8080
+
+## Exporting configuration
+
+Export the configuration is easy. Do the following in the project folder and
+inside your container:
+
+    make export
+
+## Cleaning
+
+Cleaning is simple and can be run directly outside the container:
+
+    make clean
+
+Then the project is ready to be provisioned again into a container.
+
+Production
+----------
+
+Prodution provisioning example:
+
+    make production                                 # setup environment
+    sudo vim settings.prod.php                      # add db info
+    sudo vim services.prod.yml                      # customize
+    sudo vim /var/www/data/drupal-8/sites/sites.php # add site into the pool
+    make initdb                                     # initialize db from a dump
diff --git a/share/templater/drupal-composer/files/default.services.yml b/share/templater/drupal-composer/files/default.services.yml
new file mode 100644
index 0000000..e1bbbc7
--- /dev/null
+++ b/share/templater/drupal-composer/files/default.services.yml
@@ -0,0 +1,174 @@
+parameters:
+  session.storage.options:
+    # Default ini options for sessions.
+    #
+    # Some distributions of Linux (most notably Debian) ship their PHP
+    # installations with garbage collection (gc) disabled. Since Drupal depends
+    # on PHP's garbage collection for clearing sessions, ensure that garbage
+    # collection occurs by using the most common settings.
+    # @default 1
+    gc_probability: 1
+    # @default 100
+    gc_divisor: 100
+    #
+    # Set session lifetime (in seconds), i.e. the time from the user's last
+    # visit to the active session may be deleted by the session garbage
+    # collector. When a session is deleted, authenticated users are logged out,
+    # and the contents of the user's $_SESSION variable is discarded.
+    # @default 200000
+    gc_maxlifetime: 200000
+    #
+    # Set session cookie lifetime (in seconds), i.e. the time from the session
+    # is created to the cookie expires, i.e. when the browser is expected to
+    # discard the cookie. The value 0 means "until the browser is closed".
+    # @default 2000000
+    cookie_lifetime: 2000000
+    #
+    # Drupal automatically generates a unique session cookie name based on the
+    # full domain name used to access the site. This mechanism is sufficient
+    # for most use-cases, including multi-site deployments. However, if it is
+    # desired that a session can be reused across different subdomains, the
+    # cookie domain needs to be set to the shared base domain. Doing so assures
+    # that users remain logged in as they cross between various subdomains.
+    # To maximize compatibility and normalize the behavior across user agents,
+    # the cookie domain should start with a dot.
+    #
+    # @default none
+    # cookie_domain: '.example.com'
+    #
+  twig.config:
+    # Twig debugging:
+    #
+    # When debugging is enabled:
+    # - The markup of each Twig template is surrounded by HTML comments that
+    #   contain theming information, such as template file name suggestions.
+    # - Note that this debugging markup will cause automated tests that directly
+    #   check rendered HTML to fail. When running automated tests, 'debug'
+    #   should be set to FALSE.
+    # - The dump() function can be used in Twig templates to output information
+    #   about template variables.
+    # - Twig templates are automatically recompiled whenever the source code
+    #   changes (see auto_reload below).
+    #
+    # For more information about debugging Twig templates, see
+    # https://www.drupal.org/node/1906392.
+    #
+    # Not recommended in production environments
+    # @default false
+    debug: false
+    # Twig auto-reload:
+    #
+    # Automatically recompile Twig templates whenever the source code changes.
+    # If you don't provide a value for auto_reload, it will be determined
+    # based on the value of debug.
+    #
+    # Not recommended in production environments
+    # @default null
+    auto_reload: null
+    # Twig cache:
+    #
+    # By default, Twig templates will be compiled and stored in the filesystem
+    # to increase performance. Disabling the Twig cache will recompile the
+    # templates from source each time they are used. In most cases the
+    # auto_reload setting above should be enabled rather than disabling the
+    # Twig cache.
+    #
+    # Not recommended in production environments
+    # @default true
+    cache: true
+  renderer.config:
+    # Renderer required cache contexts:
+    #
+    # The Renderer will automatically associate these cache contexts with every
+    # render array, hence varying every render array by these cache contexts.
+    #
+    # @default ['languages:language_interface', 'theme', 'user.permissions']
+    required_cache_contexts: ['languages:language_interface', 'theme', 'user.permissions']
+    # Renderer automatic placeholdering conditions:
+    #
+    # Drupal allows portions of the page to be automatically deferred when
+    # rendering to improve cache performance. That is especially helpful for
+    # cache contexts that vary widely, such as the active user. On some sites
+    # those may be different, however, such as sites with only a handful of
+    # users. If you know what the high-cardinality cache contexts are for your
+    # site, specify those here. If you're not sure, the defaults are fairly safe
+    # in general.
+    #
+    # For more information about rendering optimizations see
+    # https://www.drupal.org/developing/api/8/render/arrays/cacheability#optimizing
+    auto_placeholder_conditions:
+      # Max-age at or below which caching is not considered worthwhile.
+      #
+      # Disable by setting to -1.
+      #
+      # @default 0
+      max-age: 0
+      # Cache contexts with a high cardinality.
+      #
+      # Disable by setting to [].
+      #
+      # @default ['session', 'user']
+      contexts: ['session', 'user']
+      # Tags with a high invalidation frequency.
+      #
+      # Disable by setting to [].
+      #
+      # @default []
+      tags: []
+  # Cacheability debugging:
+  #
+  # Responses with cacheability metadata (CacheableResponseInterface instances)
+  # get X-Drupal-Cache-Tags and X-Drupal-Cache-Contexts headers.
+  #
+  # For more information about debugging cacheable responses, see
+  # https://www.drupal.org/developing/api/8/response/cacheable-response-interface
+  #
+  # Not recommended in production environments
+  # @default false
+  http.response.debug_cacheability_headers: false
+  factory.keyvalue:
+    {}
+    # Default key/value storage service to use.
+    # @default keyvalue.database
+    # default: keyvalue.database
+    # Collection-specific overrides.
+    # state: keyvalue.database
+  factory.keyvalue.expirable:
+    {}
+    # Default key/value expirable storage service to use.
+    # @default keyvalue.database.expirable
+    # default: keyvalue.database.expirable
+  # Allowed protocols for URL generation.
+  filter_protocols:
+    - http
+    - https
+    - ftp
+    - news
+    - nntp
+    - tel
+    - telnet
+    - mailto
+    - irc
+    - ssh
+    - sftp
+    - webcal
+    - rtsp
+
+   # Configure Cross-Site HTTP requests (CORS).
+   # Read https://developer.mozilla.org/en-US/docs/Web/HTTP/Access_control_CORS
+   # for more information about the topic in general.
+   # Note: By default the configuration is disabled.
+  cors.config:
+    enabled: false
+    # Specify allowed headers, like 'x-allowed-header'.
+    allowedHeaders: []
+    # Specify allowed request methods, specify ['*'] to allow all possible ones.
+    allowedMethods: []
+    # Configure requests allowed from specific origins.
+    allowedOrigins: ['*']
+    # Sets the Access-Control-Expose-Headers header.
+    exposedHeaders: false
+    # Sets the Access-Control-Max-Age header.
+    maxAge: false
+    # Sets the Access-Control-Allow-Credentials header.
+    supportsCredentials: false
diff --git a/share/templater/drupal-composer/files/default.settings.php b/share/templater/drupal-composer/files/default.settings.php
new file mode 100644
index 0000000..59afc6c
--- /dev/null
+++ b/share/templater/drupal-composer/files/default.settings.php
@@ -0,0 +1,804 @@
+<?php
+
+/**
+ * @file
+ * Drupal site-specific configuration file.
+ *
+ * IMPORTANT NOTE:
+ * This file may have been set to read-only by the Drupal installation program.
+ * If you make changes to this file, be sure to protect it again after making
+ * your modifications. Failure to remove write permissions to this file is a
+ * security risk.
+ *
+ * In order to use the selection rules below the multisite aliasing file named
+ * sites/sites.php must be present. Its optional settings will be loaded, and
+ * the aliases in the array $sites will override the default directory rules
+ * below. See sites/example.sites.php for more information about aliases.
+ *
+ * The configuration directory will be discovered by stripping the website's
+ * hostname from left to right and pathname from right to left. The first
+ * configuration file found will be used and any others will be ignored. If no
+ * other configuration file is found then the default configuration file at
+ * 'sites/default' will be used.
+ *
+ * For example, for a fictitious site installed at
+ * https://www.drupal.org:8080/mysite/test/, the 'settings.php' file is searched
+ * for in the following directories:
+ *
+ * - sites/8080.www.drupal.org.mysite.test
+ * - sites/www.drupal.org.mysite.test
+ * - sites/drupal.org.mysite.test
+ * - sites/org.mysite.test
+ *
+ * - sites/8080.www.drupal.org.mysite
+ * - sites/www.drupal.org.mysite
+ * - sites/drupal.org.mysite
+ * - sites/org.mysite
+ *
+ * - sites/8080.www.drupal.org
+ * - sites/www.drupal.org
+ * - sites/drupal.org
+ * - sites/org
+ *
+ * - sites/default
+ *
+ * Note that if you are installing on a non-standard port number, prefix the
+ * hostname with that number. For example,
+ * https://www.drupal.org:8080/mysite/test/ could be loaded from
+ * sites/8080.www.drupal.org.mysite.test/.
+ *
+ * @see example.sites.php
+ * @see \Drupal\Core\DrupalKernel::getSitePath()
+ *
+ * In addition to customizing application settings through variables in
+ * settings.php, you can create a services.yml file in the same directory to
+ * register custom, site-specific service definitions and/or swap out default
+ * implementations with custom ones.
+ */
+
+/**
+ * Database settings:
+ *
+ * The $databases array specifies the database connection or
+ * connections that Drupal may use.  Drupal is able to connect
+ * to multiple databases, including multiple types of databases,
+ * during the same request.
+ *
+ * One example of the simplest connection array is shown below. To use the
+ * sample settings, copy and uncomment the code below between the @code and
+ * @endcode lines and paste it after the $databases declaration. You will need
+ * to replace the database username and password and possibly the host and port
+ * with the appropriate credentials for your database system.
+ *
+ * The next section describes how to customize the $databases array for more
+ * specific needs.
+ *
+ * @code
+ * $databases['default']['default'] = array (
+ *   'database' => 'databasename',
+ *   'username' => 'sqlusername',
+ *   'password' => 'sqlpassword',
+ *   'host' => 'localhost',
+ *   'port' => '3306',
+ *   'driver' => 'mysql',
+ *   'prefix' => '',
+ *   'collation' => 'utf8mb4_general_ci',
+ * );
+ * @endcode
+ */
+$databases = array();
+
+/**
+ * Customizing database settings.
+ *
+ * Many of the values of the $databases array can be customized for your
+ * particular database system. Refer to the sample in the section above as a
+ * starting point.
+ *
+ * The "driver" property indicates what Drupal database driver the
+ * connection should use.  This is usually the same as the name of the
+ * database type, such as mysql or sqlite, but not always.  The other
+ * properties will vary depending on the driver.  For SQLite, you must
+ * specify a database file name in a directory that is writable by the
+ * webserver.  For most other drivers, you must specify a
+ * username, password, host, and database name.
+ *
+ * Transaction support is enabled by default for all drivers that support it,
+ * including MySQL. To explicitly disable it, set the 'transactions' key to
+ * FALSE.
+ * Note that some configurations of MySQL, such as the MyISAM engine, don't
+ * support it and will proceed silently even if enabled. If you experience
+ * transaction related crashes with such configuration, set the 'transactions'
+ * key to FALSE.
+ *
+ * For each database, you may optionally specify multiple "target" databases.
+ * A target database allows Drupal to try to send certain queries to a
+ * different database if it can but fall back to the default connection if not.
+ * That is useful for primary/replica replication, as Drupal may try to connect
+ * to a replica server when appropriate and if one is not available will simply
+ * fall back to the single primary server (The terms primary/replica are
+ * traditionally referred to as master/slave in database server documentation).
+ *
+ * The general format for the $databases array is as follows:
+ * @code
+ * $databases['default']['default'] = $info_array;
+ * $databases['default']['replica'][] = $info_array;
+ * $databases['default']['replica'][] = $info_array;
+ * $databases['extra']['default'] = $info_array;
+ * @endcode
+ *
+ * In the above example, $info_array is an array of settings described above.
+ * The first line sets a "default" database that has one primary database
+ * (the second level default).  The second and third lines create an array
+ * of potential replica databases.  Drupal will select one at random for a given
+ * request as needed.  The fourth line creates a new database with a name of
+ * "extra".
+ *
+ * You can optionally set prefixes for some or all database table names
+ * by using the 'prefix' setting. If a prefix is specified, the table
+ * name will be prepended with its value. Be sure to use valid database
+ * characters only, usually alphanumeric and underscore. If no prefixes
+ * are desired, leave it as an empty string ''.
+ *
+ * To have all database names prefixed, set 'prefix' as a string:
+ * @code
+ *   'prefix' => 'main_',
+ * @endcode
+ *
+ * Per-table prefixes are deprecated as of Drupal 8.2, and will be removed in
+ * Drupal 9.0. After that, only a single prefix for all tables will be
+ * supported.
+ *
+ * To provide prefixes for specific tables, set 'prefix' as an array.
+ * The array's keys are the table names and the values are the prefixes.
+ * The 'default' element is mandatory and holds the prefix for any tables
+ * not specified elsewhere in the array. Example:
+ * @code
+ *   'prefix' => array(
+ *     'default'   => 'main_',
+ *     'users'     => 'shared_',
+ *     'sessions'  => 'shared_',
+ *     'role'      => 'shared_',
+ *     'authmap'   => 'shared_',
+ *   ),
+ * @endcode
+ * You can also use a reference to a schema/database as a prefix. This may be
+ * useful if your Drupal installation exists in a schema that is not the default
+ * or you want to access several databases from the same code base at the same
+ * time.
+ * Example:
+ * @code
+ *   'prefix' => array(
+ *     'default'   => 'main.',
+ *     'users'     => 'shared.',
+ *     'sessions'  => 'shared.',
+ *     'role'      => 'shared.',
+ *     'authmap'   => 'shared.',
+ *   );
+ * @endcode
+ * NOTE: MySQL and SQLite's definition of a schema is a database.
+ *
+ * Advanced users can add or override initial commands to execute when
+ * connecting to the database server, as well as PDO connection settings. For
+ * example, to enable MySQL SELECT queries to exceed the max_join_size system
+ * variable, and to reduce the database connection timeout to 5 seconds:
+ * @code
+ * $databases['default']['default'] = array(
+ *   'init_commands' => array(
+ *     'big_selects' => 'SET SQL_BIG_SELECTS=1',
+ *   ),
+ *   'pdo' => array(
+ *     PDO::ATTR_TIMEOUT => 5,
+ *   ),
+ * );
+ * @endcode
+ *
+ * WARNING: The above defaults are designed for database portability. Changing
+ * them may cause unexpected behavior, including potential data loss. See
+ * https://www.drupal.org/developing/api/database/configuration for more
+ * information on these defaults and the potential issues.
+ *
+ * More details can be found in the constructor methods for each driver:
+ * - \Drupal\Core\Database\Driver\mysql\Connection::__construct()
+ * - \Drupal\Core\Database\Driver\pgsql\Connection::__construct()
+ * - \Drupal\Core\Database\Driver\sqlite\Connection::__construct()
+ *
+ * Sample Database configuration format for PostgreSQL (pgsql):
+ * @code
+ *   $databases['default']['default'] = array(
+ *     'driver' => 'pgsql',
+ *     'database' => 'databasename',
+ *     'username' => 'sqlusername',
+ *     'password' => 'sqlpassword',
+ *     'host' => 'localhost',
+ *     'prefix' => '',
+ *   );
+ * @endcode
+ *
+ * Sample Database configuration format for SQLite (sqlite):
+ * @code
+ *   $databases['default']['default'] = array(
+ *     'driver' => 'sqlite',
+ *     'database' => '/path/to/databasefilename',
+ *   );
+ * @endcode
+ */
+
+/**
+ * Location of the site configuration files.
+ *
+ * The $config_directories array specifies the location of file system
+ * directories used for configuration data. On install, the "sync" directory is
+ * created. This is used for configuration imports. The "active" directory is
+ * not created by default since the default storage for active configuration is
+ * the database rather than the file system. (This can be changed. See "Active
+ * configuration settings" below).
+ *
+ * The default location for the "sync" directory is inside a randomly-named
+ * directory in the public files path. The setting below allows you to override
+ * the "sync" location.
+ *
+ * If you use files for the "active" configuration, you can tell the
+ * Configuration system where this directory is located by adding an entry with
+ * array key CONFIG_ACTIVE_DIRECTORY.
+ *
+ * Example:
+ * @code
+ *   $config_directories = array(
+ *     CONFIG_SYNC_DIRECTORY => '/directory/outside/webroot',
+ *   );
+ * @endcode
+ */
+$config_directories = array();
+
+/**
+ * Settings:
+ *
+ * $settings contains environment-specific configuration, such as the files
+ * directory and reverse proxy address, and temporary configuration, such as
+ * security overrides.
+ *
+ * @see \Drupal\Core\Site\Settings::get()
+ */
+
+/**
+ * The active installation profile.
+ *
+ * Changing this after installation is not recommended as it changes which
+ * directories are scanned during extension discovery. If this is set prior to
+ * installation this value will be rewritten according to the profile selected
+ * by the user.
+ *
+ * @see install_select_profile()
+ *
+ * @deprecated in Drupal 8.3.0 and will be removed before Drupal 9.0.0. The
+ *   install profile is written to the core.extension configuration. If a
+ *   service requires the install profile use the 'install_profile' container
+ *   parameter. Functional code can use \Drupal::installProfile().
+ */
+# $settings['install_profile'] = '';
+
+/**
+ * Salt for one-time login links, cancel links, form tokens, etc.
+ *
+ * This variable will be set to a random value by the installer. All one-time
+ * login links will be invalidated if the value is changed. Note that if your
+ * site is deployed on a cluster of web servers, you must ensure that this
+ * variable has the same value on each server.
+ *
+ * For enhanced security, you may set this variable to the contents of a file
+ * outside your document root; you should also ensure that this file is not
+ * stored with backups of your database.
+ *
+ * Example:
+ * @code
+ *   $settings['hash_salt'] = file_get_contents('/home/example/salt.txt');
+ * @endcode
+ */
+$settings['hash_salt'] = '';
+
+/**
+ * Deployment identifier.
+ *
+ * Drupal's dependency injection container will be automatically invalidated and
+ * rebuilt when the Drupal core version changes. When updating contributed or
+ * custom code that changes the container, changing this identifier will also
+ * allow the container to be invalidated as soon as code is deployed.
+ */
+# $settings['deployment_identifier'] = \Drupal::VERSION;
+
+/**
+ * Access control for update.php script.
+ *
+ * If you are updating your Drupal installation using the update.php script but
+ * are not logged in using either an account with the "Administer software
+ * updates" permission or the site maintenance account (the account that was
+ * created during installation), you will need to modify the access check
+ * statement below. Change the FALSE to a TRUE to disable the access check.
+ * After finishing the upgrade, be sure to open this file again and change the
+ * TRUE back to a FALSE!
+ */
+$settings['update_free_access'] = FALSE;
+
+/**
+ * External access proxy settings:
+ *
+ * If your site must access the Internet via a web proxy then you can enter the
+ * proxy settings here. Set the full URL of the proxy, including the port, in
+ * variables:
+ * - $settings['http_client_config']['proxy']['http']: The proxy URL for HTTP
+ *   requests.
+ * - $settings['http_client_config']['proxy']['https']: The proxy URL for HTTPS
+ *   requests.
+ * You can pass in the user name and password for basic authentication in the
+ * URLs in these settings.
+ *
+ * You can also define an array of host names that can be accessed directly,
+ * bypassing the proxy, in $settings['http_client_config']['proxy']['no'].
+ */
+# $settings['http_client_config']['proxy']['http'] = 'http://proxy_user:proxy_pass@example.com:8080';
+# $settings['http_client_config']['proxy']['https'] = 'http://proxy_user:proxy_pass@example.com:8080';
+# $settings['http_client_config']['proxy']['no'] = ['127.0.0.1', 'localhost'];
+
+/**
+ * Reverse Proxy Configuration:
+ *
+ * Reverse proxy servers are often used to enhance the performance
+ * of heavily visited sites and may also provide other site caching,
+ * security, or encryption benefits. In an environment where Drupal
+ * is behind a reverse proxy, the real IP address of the client should
+ * be determined such that the correct client IP address is available
+ * to Drupal's logging, statistics, and access management systems. In
+ * the most simple scenario, the proxy server will add an
+ * X-Forwarded-For header to the request that contains the client IP
+ * address. However, HTTP headers are vulnerable to spoofing, where a
+ * malicious client could bypass restrictions by setting the
+ * X-Forwarded-For header directly. Therefore, Drupal's proxy
+ * configuration requires the IP addresses of all remote proxies to be
+ * specified in $settings['reverse_proxy_addresses'] to work correctly.
+ *
+ * Enable this setting to get Drupal to determine the client IP from
+ * the X-Forwarded-For header (or $settings['reverse_proxy_header'] if set).
+ * If you are unsure about this setting, do not have a reverse proxy,
+ * or Drupal operates in a shared hosting environment, this setting
+ * should remain commented out.
+ *
+ * In order for this setting to be used you must specify every possible
+ * reverse proxy IP address in $settings['reverse_proxy_addresses'].
+ * If a complete list of reverse proxies is not available in your
+ * environment (for example, if you use a CDN) you may set the
+ * $_SERVER['REMOTE_ADDR'] variable directly in settings.php.
+ * Be aware, however, that it is likely that this would allow IP
+ * address spoofing unless more advanced precautions are taken.
+ */
+# $settings['reverse_proxy'] = TRUE;
+
+/**
+ * Specify every reverse proxy IP address in your environment.
+ * This setting is required if $settings['reverse_proxy'] is TRUE.
+ */
+# $settings['reverse_proxy_addresses'] = array('a.b.c.d', ...);
+
+/**
+ * Set this value if your proxy server sends the client IP in a header
+ * other than X-Forwarded-For.
+ */
+# $settings['reverse_proxy_header'] = 'X_CLUSTER_CLIENT_IP';
+
+/**
+ * Set this value if your proxy server sends the client protocol in a header
+ * other than X-Forwarded-Proto.
+ */
+# $settings['reverse_proxy_proto_header'] = 'X_FORWARDED_PROTO';
+
+/**
+ * Set this value if your proxy server sends the client protocol in a header
+ * other than X-Forwarded-Host.
+ */
+# $settings['reverse_proxy_host_header'] = 'X_FORWARDED_HOST';
+
+/**
+ * Set this value if your proxy server sends the client protocol in a header
+ * other than X-Forwarded-Port.
+ */
+# $settings['reverse_proxy_port_header'] = 'X_FORWARDED_PORT';
+
+/**
+ * Set this value if your proxy server sends the client protocol in a header
+ * other than Forwarded.
+ */
+# $settings['reverse_proxy_forwarded_header'] = 'FORWARDED';
+
+/**
+ * Page caching:
+ *
+ * By default, Drupal sends a "Vary: Cookie" HTTP header for anonymous page
+ * views. This tells a HTTP proxy that it may return a page from its local
+ * cache without contacting the web server, if the user sends the same Cookie
+ * header as the user who originally requested the cached page. Without "Vary:
+ * Cookie", authenticated users would also be served the anonymous page from
+ * the cache. If the site has mostly anonymous users except a few known
+ * editors/administrators, the Vary header can be omitted. This allows for
+ * better caching in HTTP proxies (including reverse proxies), i.e. even if
+ * clients send different cookies, they still get content served from the cache.
+ * However, authenticated users should access the site directly (i.e. not use an
+ * HTTP proxy, and bypass the reverse proxy if one is used) in order to avoid
+ * getting cached pages from the proxy.
+ */
+# $settings['omit_vary_cookie'] = TRUE;
+
+
+/**
+ * Cache TTL for client error (4xx) responses.
+ *
+ * Items cached per-URL tend to result in a large number of cache items, and
+ * this can be problematic on 404 pages which by their nature are unbounded. A
+ * fixed TTL can be set for these items, defaulting to one hour, so that cache
+ * backends which do not support LRU can purge older entries. To disable caching
+ * of client error responses set the value to 0. Currently applies only to
+ * page_cache module.
+ */
+# $settings['cache_ttl_4xx'] = 3600;
+
+/**
+ * Expiration of cached forms.
+ *
+ * Drupal's Form API stores details of forms in a cache and these entries are
+ * kept for at least 6 hours by default. Expired entries are cleared by cron.
+ *
+ * @see \Drupal\Core\Form\FormCache::setCache()
+ */
+# $settings['form_cache_expiration'] = 21600;
+
+/**
+ * Class Loader.
+ *
+ * If the APC extension is detected, the Symfony APC class loader is used for
+ * performance reasons. Detection can be prevented by setting
+ * class_loader_auto_detect to false, as in the example below.
+ */
+# $settings['class_loader_auto_detect'] = FALSE;
+
+/*
+ * If the APC extension is not detected, either because APC is missing or
+ * because auto-detection has been disabled, auto-loading falls back to
+ * Composer's ClassLoader, which is good for development as it does not break
+ * when code is moved in the file system. You can also decorate the base class
+ * loader with another cached solution than the Symfony APC class loader, as
+ * all production sites should have a cached class loader of some sort enabled.
+ *
+ * To do so, you may decorate and replace the local $class_loader variable. For
+ * example, to use Symfony's APC class loader without automatic detection,
+ * uncomment the code below.
+ */
+/*
+if ($settings['hash_salt']) {
+  $prefix = 'drupal.' . hash('sha256', 'drupal.' . $settings['hash_salt']);
+  $apc_loader = new \Symfony\Component\ClassLoader\ApcClassLoader($prefix, $class_loader);
+  unset($prefix);
+  $class_loader->unregister();
+  $apc_loader->register();
+  $class_loader = $apc_loader;
+}
+*/
+
+/**
+ * Authorized file system operations:
+ *
+ * The Update Manager module included with Drupal provides a mechanism for
+ * site administrators to securely install missing updates for the site
+ * directly through the web user interface. On securely-configured servers,
+ * the Update manager will require the administrator to provide SSH or FTP
+ * credentials before allowing the installation to proceed; this allows the
+ * site to update the new files as the user who owns all the Drupal files,
+ * instead of as the user the webserver is running as. On servers where the
+ * webserver user is itself the owner of the Drupal files, the administrator
+ * will not be prompted for SSH or FTP credentials (note that these server
+ * setups are common on shared hosting, but are inherently insecure).
+ *
+ * Some sites might wish to disable the above functionality, and only update
+ * the code directly via SSH or FTP themselves. This setting completely
+ * disables all functionality related to these authorized file operations.
+ *
+ * @see https://www.drupal.org/node/244924
+ *
+ * Remove the leading hash signs to disable.
+ */
+# $settings['allow_authorize_operations'] = FALSE;
+
+/**
+ * Default mode for directories and files written by Drupal.
+ *
+ * Value should be in PHP Octal Notation, with leading zero.
+ */
+# $settings['file_chmod_directory'] = 0775;
+# $settings['file_chmod_file'] = 0664;
+
+/**
+ * Public file base URL:
+ *
+ * An alternative base URL to be used for serving public files. This must
+ * include any leading directory path.
+ *
+ * A different value from the domain used by Drupal to be used for accessing
+ * public files. This can be used for a simple CDN integration, or to improve
+ * security by serving user-uploaded files from a different domain or subdomain
+ * pointing to the same server. Do not include a trailing slash.
+ */
+# $settings['file_public_base_url'] = 'http://downloads.example.com/files';
+
+/**
+ * Public file path:
+ *
+ * A local file system path where public files will be stored. This directory
+ * must exist and be writable by Drupal. This directory must be relative to
+ * the Drupal installation directory and be accessible over the web.
+ */
+# $settings['file_public_path'] = 'sites/default/files';
+
+/**
+ * Private file path:
+ *
+ * A local file system path where private files will be stored. This directory
+ * must be absolute, outside of the Drupal installation directory and not
+ * accessible over the web.
+ *
+ * Note: Caches need to be cleared when this value is changed to make the
+ * private:// stream wrapper available to the system.
+ *
+ * See https://www.drupal.org/documentation/modules/file for more information
+ * about securing private files.
+ */
+# $settings['file_private_path'] = '';
+
+/**
+ * Session write interval:
+ *
+ * Set the minimum interval between each session write to database.
+ * For performance reasons it defaults to 180.
+ */
+# $settings['session_write_interval'] = 180;
+
+/**
+ * String overrides:
+ *
+ * To override specific strings on your site with or without enabling the Locale
+ * module, add an entry to this list. This functionality allows you to change
+ * a small number of your site's default English language interface strings.
+ *
+ * Remove the leading hash signs to enable.
+ *
+ * The "en" part of the variable name, is dynamic and can be any langcode of
+ * any added language. (eg locale_custom_strings_de for german).
+ */
+# $settings['locale_custom_strings_en'][''] = array(
+#   'forum'      => 'Discussion board',
+#   '@count min' => '@count minutes',
+# );
+
+/**
+ * A custom theme for the offline page:
+ *
+ * This applies when the site is explicitly set to maintenance mode through the
+ * administration page or when the database is inactive due to an error.
+ * The template file should also be copied into the theme. It is located inside
+ * 'core/modules/system/templates/maintenance-page.html.twig'.
+ *
+ * Note: This setting does not apply to installation and update pages.
+ */
+# $settings['maintenance_theme'] = 'bartik';
+
+/**
+ * PHP settings:
+ *
+ * To see what PHP settings are possible, including whether they can be set at
+ * runtime (by using ini_set()), read the PHP documentation:
+ * http://php.net/manual/ini.list.php
+ * See \Drupal\Core\DrupalKernel::bootEnvironment() for required runtime
+ * settings and the .htaccess file for non-runtime settings.
+ * Settings defined there should not be duplicated here so as to avoid conflict
+ * issues.
+ */
+
+/**
+ * If you encounter a situation where users post a large amount of text, and
+ * the result is stripped out upon viewing but can still be edited, Drupal's
+ * output filter may not have sufficient memory to process it.  If you
+ * experience this issue, you may wish to uncomment the following two lines
+ * and increase the limits of these variables.  For more information, see
+ * http://php.net/manual/pcre.configuration.php.
+ */
+# ini_set('pcre.backtrack_limit', 200000);
+# ini_set('pcre.recursion_limit', 200000);
+
+/**
+ * Active configuration settings.
+ *
+ * By default, the active configuration is stored in the database in the
+ * {config} table. To use a different storage mechanism for the active
+ * configuration, do the following prior to installing:
+ * - Create an "active" directory and declare its path in $config_directories
+ *   as explained under the 'Location of the site configuration files' section
+ *   above in this file. To enhance security, you can declare a path that is
+ *   outside your document root.
+ * - Override the 'bootstrap_config_storage' setting here. It must be set to a
+ *   callable that returns an object that implements
+ *   \Drupal\Core\Config\StorageInterface.
+ * - Override the service definition 'config.storage.active'. Put this
+ *   override in a services.yml file in the same directory as settings.php
+ *   (definitions in this file will override service definition defaults).
+ */
+# $settings['bootstrap_config_storage'] = array('Drupal\Core\Config\BootstrapConfigStorageFactory', 'getFileStorage');
+
+/**
+ * Configuration overrides.
+ *
+ * To globally override specific configuration values for this site,
+ * set them here. You usually don't need to use this feature. This is
+ * useful in a configuration file for a vhost or directory, rather than
+ * the default settings.php.
+ *
+ * Note that any values you provide in these variable overrides will not be
+ * viewable from the Drupal administration interface. The administration
+ * interface displays the values stored in configuration so that you can stage
+ * changes to other environments that don't have the overrides.
+ *
+ * There are particular configuration values that are risky to override. For
+ * example, overriding the list of installed modules in 'core.extension' is not
+ * supported as module install or uninstall has not occurred. Other examples
+ * include field storage configuration, because it has effects on database
+ * structure, and 'core.menu.static_menu_link_overrides' since this is cached in
+ * a way that is not config override aware. Also, note that changing
+ * configuration values in settings.php will not fire any of the configuration
+ * change events.
+ */
+# $config['system.file']['path']['temporary'] = '/tmp';
+# $config['system.site']['name'] = 'My Drupal site';
+# $config['system.theme']['default'] = 'stark';
+# $config['user.settings']['anonymous'] = 'Visitor';
+
+/**
+ * Fast 404 pages:
+ *
+ * Drupal can generate fully themed 404 pages. However, some of these responses
+ * are for images or other resource files that are not displayed to the user.
+ * This can waste bandwidth, and also generate server load.
+ *
+ * The options below return a simple, fast 404 page for URLs matching a
+ * specific pattern:
+ * - $config['system.performance']['fast_404']['exclude_paths']: A regular
+ *   expression to match paths to exclude, such as images generated by image
+ *   styles, or dynamically-resized images. The default pattern provided below
+ *   also excludes the private file system. If you need to add more paths, you
+ *   can add '|path' to the expression.
+ * - $config['system.performance']['fast_404']['paths']: A regular expression to
+ *   match paths that should return a simple 404 page, rather than the fully
+ *   themed 404 page. If you don't have any aliases ending in htm or html you
+ *   can add '|s?html?' to the expression.
+ * - $config['system.performance']['fast_404']['html']: The html to return for
+ *   simple 404 pages.
+ *
+ * Remove the leading hash signs if you would like to alter this functionality.
+ */
+# $config['system.performance']['fast_404']['exclude_paths'] = '/\/(?:styles)|(?:system\/files)\//';
+# $config['system.performance']['fast_404']['paths'] = '/\.(?:txt|png|gif|jpe?g|css|js|ico|swf|flv|cgi|bat|pl|dll|exe|asp)$/i';
+# $config['system.performance']['fast_404']['html'] = '<!DOCTYPE html><html><head><title>404 Not Found</title></head><body><h1>Not Found</h1><p>The requested URL "@path" was not found on this server.</p></body></html>';
+
+/**
+ * Load services definition file.
+ */
+$settings['container_yamls'][] = $app_root . '/' . $site_path . '/services.yml';
+
+/**
+ * Override the default service container class.
+ *
+ * This is useful for example to trace the service container for performance
+ * tracking purposes, for testing a service container with an error condition or
+ * to test a service container that throws an exception.
+ */
+# $settings['container_base_class'] = '\Drupal\Core\DependencyInjection\Container';
+
+/**
+ * Override the default yaml parser class.
+ *
+ * Provide a fully qualified class name here if you would like to provide an
+ * alternate implementation YAML parser. The class must implement the
+ * \Drupal\Component\Serialization\SerializationInterface interface.
+ */
+# $settings['yaml_parser_class'] = NULL;
+
+/**
+ * Trusted host configuration.
+ *
+ * Drupal core can use the Symfony trusted host mechanism to prevent HTTP Host
+ * header spoofing.
+ *
+ * To enable the trusted host mechanism, you enable your allowable hosts
+ * in $settings['trusted_host_patterns']. This should be an array of regular
+ * expression patterns, without delimiters, representing the hosts you would
+ * like to allow.
+ *
+ * For example:
+ * @code
+ * $settings['trusted_host_patterns'] = array(
+ *   '^www\.example\.com$',
+ * );
+ * @endcode
+ * will allow the site to only run from www.example.com.
+ *
+ * If you are running multisite, or if you are running your site from
+ * different domain names (eg, you don't redirect http://www.example.com to
+ * http://example.com), you should specify all of the host patterns that are
+ * allowed by your site.
+ *
+ * For example:
+ * @code
+ * $settings['trusted_host_patterns'] = array(
+ *   '^example\.com$',
+ *   '^.+\.example\.com$',
+ *   '^example\.org$',
+ *   '^.+\.example\.org$',
+ * );
+ * @endcode
+ * will allow the site to run off of all variants of example.com and
+ * example.org, with all subdomains included.
+ */
+
+/**
+ * The default list of directories that will be ignored by Drupal's file API.
+ *
+ * By default ignore node_modules and bower_components folders to avoid issues
+ * with common frontend tools and recursive scanning of directories looking for
+ * extensions.
+ *
+ * @see file_scan_directory()
+ * @see \Drupal\Core\Extension\ExtensionDiscovery::scanDirectory()
+ */
+$settings['file_scan_ignore_directories'] = [
+  'node_modules',
+  'bower_components',
+  'puppet',
+];
+
+/**
+ * The default number of entities to update in a batch process.
+ *
+ * This is used by update and post-update functions that need to go through and
+ * change all the entities on a site, so it is useful to increase this number
+ * if your hosting configuration (i.e. RAM allocation, CPU speed) allows for a
+ * larger number of entities to be processed in a single batch run.
+ */
+$settings['entity_update_batch_size'] = 50;
+
+/**
+ * Basic config set by templater - https://templater.fluxo.info
+ */
+$databases['default']['default'] = array (
+  'database' => 'drupal',
+  'username' => 'drupal',
+  'password' => 'hackme',
+  'host' => 'localhost',
+  'port' => '3306',
+  'driver' => 'mysql',
+  'prefix' => '',
+  'collation' => 'utf8mb4_general_ci',
+);
+$settings['install_profile']       = 'standard';
+$config_directories['sync']        = 'sites/default/config/sync';
+$settings['trusted_host_patterns'] = array(
+  '^localhost$',
+);
+
+/**
+ * Load local development override configuration, if available.
+ *
+ * Use settings.local.php to override variables on secondary (staging,
+ * development, etc) installations of this site. Typically used to disable
+ * caching, JavaScript/CSS compression, re-routing of outgoing emails, and
+ * other things that should not happen on development and testing sites.
+ *
+ * Keep this code block at the end of this file to take full effect.
+ */
+if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) {
+  include $app_root . '/' . $site_path . '/settings.local.php';
+}
diff --git a/share/templater/drupal-composer/files/development.services.yml b/share/templater/drupal-composer/files/development.services.yml
new file mode 100644
index 0000000..d2857c6
--- /dev/null
+++ b/share/templater/drupal-composer/files/development.services.yml
@@ -0,0 +1,9 @@
+# Local development services.
+#
+# To activate this feature, follow the instructions at the top of the
+# 'example.settings.local.php' file, which sits next to this file.
+parameters:
+  http.response.debug_cacheability_headers: true
+services:
+  cache.backend.null:
+    class: Drupal\Core\Cache\NullBackendFactory
diff --git a/share/templater/drupal-composer/files/drupal.make.yml b/share/templater/drupal-composer/files/drupal.make.yml
new file mode 100644
index 0000000..38154eb
--- /dev/null
+++ b/share/templater/drupal-composer/files/drupal.make.yml
@@ -0,0 +1,9 @@
+core: 8.x
+api: '2'
+projects:
+  drupal:
+    version: ''
+  devel:
+    version: ''
+  libraries:
+    version: ''
diff --git a/share/templater/drupal-composer/files/example.settings.local.php b/share/templater/drupal-composer/files/example.settings.local.php
new file mode 100644
index 0000000..b1f73dd
--- /dev/null
+++ b/share/templater/drupal-composer/files/example.settings.local.php
@@ -0,0 +1,115 @@
+<?php
+
+/**
+ * @file
+ * Local development override configuration feature.
+ *
+ * To activate this feature, copy and rename it such that its path plus
+ * filename is 'sites/default/settings.local.php'. Then, go to the bottom of
+ * 'sites/default/settings.php' and uncomment the commented lines that mention
+ * 'settings.local.php'.
+ *
+ * If you are using a site name in the path, such as 'sites/example.com', copy
+ * this file to 'sites/example.com/settings.local.php', and uncomment the lines
+ * at the bottom of 'sites/example.com/settings.php'.
+ */
+
+/**
+ * Assertions.
+ *
+ * The Drupal project primarily uses runtime assertions to enforce the
+ * expectations of the API by failing when incorrect calls are made by code
+ * under development.
+ *
+ * @see http://php.net/assert
+ * @see https://www.drupal.org/node/2492225
+ *
+ * If you are using PHP 7.0 it is strongly recommended that you set
+ * zend.assertions=1 in the PHP.ini file (It cannot be changed from .htaccess
+ * or runtime) on development machines and to 0 in production.
+ *
+ * @see https://wiki.php.net/rfc/expectations
+ */
+assert_options(ASSERT_ACTIVE, TRUE);
+\Drupal\Component\Assertion\Handle::register();
+
+/**
+ * Enable local development services.
+ */
+$settings['container_yamls'][] = DRUPAL_ROOT . '/sites/development.services.yml';
+
+/**
+ * Show all error messages, with backtrace information.
+ *
+ * In case the error level could not be fetched from the database, as for
+ * example the database connection failed, we rely only on this value.
+ */
+$config['system.logging']['error_level'] = 'verbose';
+
+/**
+ * Disable CSS and JS aggregation.
+ */
+$config['system.performance']['css']['preprocess'] = FALSE;
+$config['system.performance']['js']['preprocess'] = FALSE;
+
+/**
+ * Disable the render cache (this includes the page cache).
+ *
+ * Note: you should test with the render cache enabled, to ensure the correct
+ * cacheability metadata is present. However, in the early stages of
+ * development, you may want to disable it.
+ *
+ * This setting disables the render cache by using the Null cache back-end
+ * defined by the development.services.yml file above.
+ *
+ * Do not use this setting until after the site is installed.
+ */
+# $settings['cache']['bins']['render'] = 'cache.backend.null';
+
+/**
+ * Disable caching for migrations.
+ *
+ * Uncomment the code below to only store migrations in memory and not in the
+ * database. This makes it easier to develop custom migrations.
+ */
+# $settings['cache']['bins']['discovery_migration'] = 'cache.backend.memory';
+
+/**
+ * Disable Dynamic Page Cache.
+ *
+ * Note: you should test with Dynamic Page Cache enabled, to ensure the correct
+ * cacheability metadata is present (and hence the expected behavior). However,
+ * in the early stages of development, you may want to disable it.
+ */
+# $settings['cache']['bins']['dynamic_page_cache'] = 'cache.backend.null';
+
+/**
+ * Allow test modules and themes to be installed.
+ *
+ * Drupal ignores test modules and themes by default for performance reasons.
+ * During development it can be useful to install test extensions for debugging
+ * purposes.
+ */
+$settings['extension_discovery_scan_tests'] = TRUE;
+
+/**
+ * Enable access to rebuild.php.
+ *
+ * This setting can be enabled to allow Drupal's php and database cached
+ * storage to be cleared via the rebuild.php page. Access to this page can also
+ * be gained by generating a query string from rebuild_token_calculator.sh and
+ * using these parameters in a request to rebuild.php.
+ */
+$settings['rebuild_access'] = TRUE;
+
+/**
+ * Skip file system permissions hardening.
+ *
+ * The system module will periodically check the permissions of your site's
+ * site directory to ensure that it is not writable by the website user. For
+ * sites that are managed with a version control system, this can cause problems
+ * when files in that directory such as settings.php are updated, because the
+ * user pulling in the changes won't have permissions to modify files in the
+ * directory.
+ */
+$settings['skip_permissions_hardening'] = TRUE;
diff --git a/share/templater/drupal-composer/files/example.sites.php b/share/templater/drupal-composer/files/example.sites.php
new file mode 100644
index 0000000..60afae7
--- /dev/null
+++ b/share/templater/drupal-composer/files/example.sites.php
@@ -0,0 +1,55 @@
+<?php
+
+/**
+ * @file
+ * Configuration file for multi-site support and directory aliasing feature.
+ *
+ * This file is required for multi-site support and also allows you to define a
+ * set of aliases that map hostnames, ports, and pathnames to configuration
+ * directories in the sites directory. These aliases are loaded prior to
+ * scanning for directories, and they are exempt from the normal discovery
+ * rules. See default.settings.php to view how Drupal discovers the
+ * configuration directory when no alias is found.
+ *
+ * Aliases are useful on development servers, where the domain name may not be
+ * the same as the domain of the live server. Since Drupal stores file paths in
+ * the database (files, system table, etc.) this will ensure the paths are
+ * correct when the site is deployed to a live server.
+ *
+ * To activate this feature, copy and rename it such that its path plus
+ * filename is 'sites/sites.php'.
+ *
+ * Aliases are defined in an associative array named $sites. The array is
+ * written in the format: '<port>.<domain>.<path>' => 'directory'. As an
+ * example, to map https://www.drupal.org:8080/mysite/test to the configuration
+ * directory sites/example.com, the array should be defined as:
+ * @code
+ * $sites = array(
+ *   '8080.www.drupal.org.mysite.test' => 'example.com',
+ * );
+ * @endcode
+ * The URL, https://www.drupal.org:8080/mysite/test/, could be a symbolic link
+ * or an Apache Alias directive that points to the Drupal root containing
+ * index.php. An alias could also be created for a subdomain. See the
+ * @link https://www.drupal.org/documentation/install online Drupal installation guide @endlink
+ * for more information on setting up domains, subdomains, and subdirectories.
+ *
+ * The following examples look for a site configuration in sites/example.com:
+ * @code
+ * URL: http://dev.drupal.org
+ * $sites['dev.drupal.org'] = 'example.com';
+ *
+ * URL: http://localhost/example
+ * $sites['localhost.example'] = 'example.com';
+ *
+ * URL: http://localhost:8080/example
+ * $sites['8080.localhost.example'] = 'example.com';
+ *
+ * URL: https://www.drupal.org:8080/mysite/test/
+ * $sites['8080.www.drupal.org.mysite.test'] = 'example.com';
+ * @endcode
+ *
+ * @see default.settings.php
+ * @see \Drupal\Core\DrupalKernel::getSitePath()
+ * @see https://www.drupal.org/documentation/install/multi-site
+ */
diff --git a/share/templater/drupal-composer/files/puppet/Puppetfile b/share/templater/drupal-composer/files/puppet/Puppetfile
new file mode 100644
index 0000000..9697d6f
--- /dev/null
+++ b/share/templater/drupal-composer/files/puppet/Puppetfile
@@ -0,0 +1,45 @@
+# Basic modules
+mod "augeas",
+  :git => "https://git.fluxo.info/puppet-augeas"
+mod "backup",
+  :git => "https://git.fluxo.info/puppet-backup"
+mod "backupninja",
+  :git => "https://git.fluxo.info/puppet-backupninja",
+  :ref => "develop"
+mod "concat",
+  :git => "https://git.fluxo.info/puppet-concat"
+mod "cron",
+  :git => "https://git.fluxo.info/puppet-cron"
+mod "domain_check",
+  :git => "https://git.fluxo.info/puppet-domain_check"
+mod "exim",
+  :git => "https://git.fluxo.info/puppet-exim"
+mod "lsb",
+  :git => "https://git.fluxo.info/puppet-lsb"
+mod "nodo",
+  :git => "https://git.fluxo.info/puppet-nodo"
+mod "rsyslog",
+  :git => "https://git.fluxo.info/puppet-rsyslog"
+mod "shellprompt",
+  :git => "https://git.fluxo.info/shellprompt"
+mod "sshd",
+  :git => "https://git.fluxo.info/puppet-sshd",
+  :ref => "develop"
+mod "ssl",
+  :git => "https://git.fluxo.info/puppet-ssl"
+mod "stdlib",
+  :git => "https://git.fluxo.info/puppet-stdlib"
+mod "user",
+  :git => "https://git.fluxo.info/puppet-user"
+
+# Additional modules
+mod "mysql",
+  :git => "https://git.fluxo.info/puppet-mysql"
+mod "database",
+  :git => "https://git.fluxo.info/puppet-database"
+mod "apache",
+  :git => "https://git.fluxo.info/puppet-apache"
+mod "php",
+  :git => "https://git.fluxo.info/puppet-php"
+mod "drupal",
+  :git => "https://git.fluxo.info/puppet-drupal"
diff --git a/share/templater/drupal-composer/files/settings.local.php b/share/templater/drupal-composer/files/settings.local.php
new file mode 100644
index 0000000..5f4746f
--- /dev/null
+++ b/share/templater/drupal-composer/files/settings.local.php
@@ -0,0 +1 @@
+<?php // Put your local customizations here
diff --git a/share/templater/drupal-composer/setup b/share/templater/drupal-composer/setup
new file mode 100755
index 0000000..4b82243
--- /dev/null
+++ b/share/templater/drupal-composer/setup
@@ -0,0 +1,77 @@
+#!/bin/bash
+#
+# Basic files templater module.
+#
+
+# Parameters
+SHARE="$1"
+
+# Include basic functions
+source $SHARE/templater/functions || exit 1
+
+# Drupal8 implementation
+function templater_drupal8 {
+  if [ ! -e 'settings.php' ]; then
+    templater_echo "Setting up Drupal 8..."
+
+    if [ ! -e ".gitignore" ] || ! grep -q "^settings.php" .gitignore; then
+      echo web/sites/default/settings.php       >> .gitignore
+      echo web/sites/default/settings.local.php >> .gitignore
+      echo web/sites/default/settings.prod.php  >> .gitignore
+      echo web/sites/default/services.yml       >> .gitignore
+      echo web/sites/default/files              >> .gitignore
+      echo sql                                  >> .gitignore
+    fi
+
+    mkdir -p web/sites/default
+
+    if [ ! -e "settings.dev.php" ]; then
+      cp $SHARE/drupal8/files/default.settings.php web/sites/default/settings.dev.php
+      #cp $SHARE/drupal8/files/default.settings.php .
+    fi
+
+    ln -sf settings.dev.php settings.php
+
+    if [ ! -e "settings.local.php" ]; then
+      cp $SHARE/drupal7/files/settings.local.php web/sites/default/settings.local.php
+    fi
+
+    if [ ! -e "services.yml" ]; then
+      cp $SHARE/drupal8/files/default.services.yml web/sites/default/services.dev.yml
+      #cp $SHARE/drupal8/files/default.services.yml .
+    fi
+
+    ln -sf services.dev.yml services.yml
+
+    templater_install_makefile $SHARE/drupal8/files/Makefile.drupal-composer
+
+    if [ ! -e "drupal.make.yml" ]; then
+      cp $SHARE/drupal8/files/drupal.make.yml .
+    fi
+
+    if [ ! -e "README.drupal-composer.md" ]; then
+      cp $SHARE/drupal8/files/README.drupal-composer.md .
+    fi
+
+    if [ -d "puppet" ] && [ ! -e "puppet/Puppetfile" ]; then
+      cp $SHARE/drupal8/files/puppet/Puppetfile puppet/
+    else
+      cp $SHARE/drupal8/files/puppet/Puppetfile puppet/Puppetfile.drupal-composer
+    fi
+
+    # Use pushtodeploy instead
+    #if [ ! -e "bin/post-receive" ]; then
+    #  mkdir -p bin && cp $SHARE/drupal8/files/bin/post-receive bin/
+    #fi
+    templater_echo "Please use pushtodeploy module for automatede deploymends"
+
+    mkdir -p files config/sync themes modules libraries vendor
+    touch {files,config/sync,themes,modules,libraries,vendor}/.empty
+    git add -f {files,config/sync,themes,modules,libraries}/.empty
+  else
+    templater_echo "Drupal already set"
+  fi
+}
+
+# Dispatch
+templater_drupal8