Varbase example configuration for Maintained by the Vardot team.
Clone or download
Pull request Compare This branch is 93 commits ahead of danmilon:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Varbase project template for

This project provides a starter kit for Varbase 8.6.x projects hosted on It is very closely based on the Varbase Composer project.

Starting a new project

To start a new Varbase 8.6.x project on, you have 2 options:

  1. Create a new project through the user interface and select "start new project from a template". Then select Varbase 8.6.x as the template. That will create a new project using this repository as a starting point.

  2. Take an existing project, add the necessary files, and push it to a Git repository. This template includes examples of how to set up a Varbase 8.6.x site. (See the "differences" section below.)

Using as a reference

You can also use this repository as a reference for your own Drupal projects, and borrow whatever code is needed. The most important parts are the file and the .platform directory.

Also see:

  • settings.php - The customized settings.php file works for both and local development, setting only those values that are needed in both. You can add additional values as documented in default.settings.php as desired.
  • settings.platformsh.php - This file contains code to map environment variables into Drupal configuration. You can add to it as needed. See the documentation for more examples of common snippets to include here.
  • scripts/platformsh - This directory contains our update script to keep this repository in sync with the Drupal Composer project. It may be safely ignored or removed.

Managing a Drupal site built with Composer

Once the site is installed, there is no difference between a site hosted on and a site hosted anywhere else. It's just Composer. See the Drupal documentation for tips on how best to leverage Composer with Drupal 8.

How does this starter kit differ from vanilla Drupal from

  1. The vendor directory (where non-Drupal code lives) and the config directory (used for syncing configuration from development to production) are outside the web root. This is a bit more secure as those files are now not web-accessible.

  2. The settings.php and settings.platformsh.php files are provided by default. The settings.platformsh.php file automatically sets up the database connection on, and allows controlling Drupal configuration from environment variables.

  3. We include recommended and .platform files that should suffice for most use cases. You are free to tweak them as needed for your particular site.