Base

Dead simple install profile that does nothing but remove the need to create your own custom profile in order to use the new convention available since Drupal 8.6 to install a new site from an exported configuration to your install profile config/sync folder and avoid having to deal with non matching UUIDs during import.

Once enabled, a Drush command also becomes available to help symlink your exported configurations folder inside the profile:

drush base:symlink

Version 3.0.1

New Version with semantic versioning and D10 compatibility!

Note

In order to use the package with composer— if you are using drupal-composer/drupal-project for example — you will need to define a custom package in your composer.json file (Just make sure you are using the latest version of the tarball - base-3.0.1.tar.gz for the current release):

"repositories": {
    "drupal8": {
        "type": "composer",
        "url": "https://packages.drupal.org/8"
    },
    "base": {
        "type": "package",
        "package": {
            "name": "drupal/base-no-core",
            "version": "3.0.0",
            "type": "drupal-profile",
            "dist": {
                "type": "tar",
                "url": "https://ftp.drupal.org/files/projects/base-3.0.1.tar.gz"
            }
        }
    }
}

Then just require your custom package:

"require": {
    "drupal/base-no-core": "^3.0.0"
}

And you can also use installer paths using composer/installers to adjust where the package needs to be installed

"extra": {
    "installer-paths": {
        "web/core": ["type:drupal-core"],
        "web/profiles/contrib/base": ["type:drupal-profile", "drupal/base-no-core"]
    }
}

Version 8.x-2.x

For more information and simple usage, please read the included README file. (https://git.drupalcode.org/project/base/blob/8.x-2.x/README.md)

Version 8.x-1.x

Might still want to use this with Drupal prior to 8.6 — Read above for more information

Profile that installs Drupal core with bare minimal settings and then enables the project base module.

Base profile looks for any module named [name]_base in your site's modules/custom/ folder then enables it.