PHPackages                             phase2/octane - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. phase2/octane

ActiveProject

phase2/octane
=============

Template for Drupal 8 sites built using the Octane distribution.

8.6.0-alpha6(7y ago)206410GPL-2.0+PHP

Since Jun 13Pushed 7y ago52 watchersCompare

[ Source](https://github.com/phase2/octane)[ Packagist](https://packagist.org/packages/phase2/octane)[ RSS](/packages/phase2-octane/feed)WikiDiscussions 8.x-4.x Synced 2mo ago

READMEChangelog (2)Dependencies (39)Versions (19)Used By (0)

Octane
======

[](#octane)

This is a composer project used to spin up a starting instance of Drupal 8 Octane. Octane is a Drupal 8 project scaffold that provides the following features:

- Uses the Acquia/Lightning distribution.
- Uses Particle for the Pattern-Lab based theme.
- Adds common modules needed by most large Drupal 8 sites.
- Provides starting configuration for Docksal.
- Provides starting configuration for Outrigger.
- (TODO) Provides starting configuration for CI on GitLabs.

Installation
------------

[](#installation)

To create a Drupal Octane project clone this repository to a directory named for your project.

Scripts for managing your site are located in the `bin` folder:

- **Native** (no docker containers) - run scripts in `./bin` directly.
- **Docksal** - run a script via `fin scriptname`.
- **Outrigger** - run a script via `rig project scriptname`.

To initialize your Drupal project, run the `init` script. It takes an optional argument to specify which "profile" to install. By default the "Lightning" profile will be used. Other options are "standard" or "minimal".

This will create the docker containers, create a database, and install Drupal. Your site will be available at `projectname.docksal` for Docksal or `projectname.vm` for Outrigger.

Docksal example:

```
fin init

```

Outrigger example:

```
rig project init

```

If configuration files are detected in the `src/config/default` directory, the site will be installed using this existing config and the profile argument will be ignored.

Custom Project Scripts
----------------------

[](#custom-project-scripts)

Custom scripts for your project should be created in the `/bin` folder and then referenced from either Outrigger or Docksal.

For Docksal, create a file within `.docksal/commands` that performs any specific Docksal setup and then calls the script in `/bin`. See the `init`command for an example.

For Outrigger, edit the `.outrigger.yml` file and add a custom script with any specific Outrigger setup and then call the script in `/bin`. See the `rig project init` script for an example.

This will create the docker containers, create a database, and install Drupal.

### Common Commands

[](#common-commands)

Each of these commands are available as either a `fin COMMAND` or `rig project COMMAND`.

- `rebuild` - Used after a git-pull to run composer, run update hooks, import config, compile theme, clear cache.
- `theme` - Used to compile the theme and then run browserstack to watch for sass, js, twig changes.

Docker Containers
-----------------

[](#docker-containers)

Outrigger uses the full `docker-composer.yml` (and `docker-compose.override.yml` locally) to define the docker containers, whereas Docksal defines a default stack and allows you to override the configuration in `.docksal/docksal.yml` which uses the same docker-compose syntax but only needs to contain the local overrides.

Default environment variables for Outrigger are defined in the `.env` file while Docksal uses the `.docksal/docksal.env` file.

The following containers will be created and used for your site:

- `web` - The Apache web container.
- `db` - The MySQL (Docksal) or MariaDB (Outrigger) database container. Default user is `admin` and pass `admin` can be changed in the environment variables or db container configuration.

### Build/CLI Container

[](#buildcli-container)

One of the main priciples of Octane is to minimize the number of tools installed on your local computer (only Composer) and instead perform most tasks within a docker "build" container that contains all the tools.

In Outrigger, this Build container is defined in the `build.yml` docker-compose file. Various application specific containers are build on the "base" container for `drush`, `composer`, and generic `cli` commands. To run a script within the build container, use the command syntax:

```
docker-compose -f build.yml run --rm cli /var/www/bin/SCRIPTNAME.sh

```

Typically you will create a `rig project SCRIPTNAME` alias for this in the `.outrigger.yml` file or create a local alias in your own `.bashrc` file. For example:

```
ddrush='docker-compose -f build.yml run --rm drush'

```

for running drush within the build container.

To open a bash shell into the Outrigger Build container, use

```
rig project bash

```

In DockSal, the Build container is called `cli` and is defined within the default services stack, much like `web` or `db` and can be overridden using the `docksal.yml` file. Docksal provides its own set of aliases for common applications such as `fin drush`, `fin composer`, etc. To run a script within the build container, use the command syntax:

```
fin exec /var/www/bin/SCRIPTNAME.sh

```

To open a bash shell into the Docksal Build/CLI container, use

```
fin bash

```

When creating a custom command for Docksal in the `.docksal/commands`directory, you can add the comment

```
#: exec_target = cli

```

to the top of your script command file to cause it to be executed within the Build/CLI container instead of running locally.

###  Health Score

32

—

LowBetter than 72% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity20

Limited adoption so far

Community24

Small or concentrated contributor base

Maturity58

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 57.9% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~106 days

Recently: every ~4 days

Total

9

Last Release

2774d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/f760c97f03cdb414012201821a9c71f01ed25562af781159671126a306b03c60?d=identicon)[febbraro](/maintainers/febbraro)

---

Top Contributors

[![mike-potter](https://avatars.githubusercontent.com/u/1200563?v=4)](https://github.com/mike-potter "mike-potter (33 commits)")[![recrit](https://avatars.githubusercontent.com/u/917446?v=4)](https://github.com/recrit "recrit (12 commits)")[![rloos289](https://avatars.githubusercontent.com/u/19877994?v=4)](https://github.com/rloos289 "rloos289 (4 commits)")[![thagler](https://avatars.githubusercontent.com/u/259747?v=4)](https://github.com/thagler "thagler (2 commits)")[![jhedstrom](https://avatars.githubusercontent.com/u/76833?v=4)](https://github.com/jhedstrom "jhedstrom (2 commits)")[![balsama](https://avatars.githubusercontent.com/u/1536654?v=4)](https://github.com/balsama "balsama (2 commits)")[![crittermike](https://avatars.githubusercontent.com/u/32261?v=4)](https://github.com/crittermike "crittermike (1 commits)")[![kreynen](https://avatars.githubusercontent.com/u/385234?v=4)](https://github.com/kreynen "kreynen (1 commits)")

###  Code Quality

TestsPHPUnit

### Embed Badge

![Health badge](/badges/phase2-octane/health.svg)

```
[![Health](https://phpackages.com/badges/phase2-octane/health.svg)](https://phpackages.com/packages/phase2-octane)
```

###  Alternatives

[voidagency/vactory_starter_kit

Vactory is a custom Drupal profile which is developed and released by VOID Agency.

1019.7k](/packages/voidagency-vactory-starter-kit)[govcms/govcms

GovCMS Drupal Distribution

18997.1k3](/packages/govcms-govcms)[drupalwxt/wxt

Project template for Drupal 10 sites built with the WxT distribution.

29159.8k8](/packages/drupalwxt-wxt)[thunder/thunder-distribution

The thunder distribution

50634.8k3](/packages/thunder-thunder-distribution)[az-digital/az_quickstart

Arizona Quickstart

50234.3k2](/packages/az-digital-az-quickstart)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)