dripyard / demo-project
Project template DripYard demo themes and dependencies
Requires
- blueoakinteractive/boi_ci: dev-symfony-7
- composer/installers: ^2.3
- cweagans/composer-patches: ^1.7
- drupal/core-composer-scaffold: ^11.1
- drupal/core-project-message: ^11.1
- drupal/core-recommended: ^11.1
Conflicts
This package is not auto-updated.
Last update: 2025-05-20 15:41:21 UTC
README
This project creates a DripYard demo installation of Drupal.
Installation
composer create-project dripyard/demo-project
Included Files
.boi_ci.yml
Provides configuration for boi_ci
, including:
- Symlink for
settings.local.php
- Symlink for
developer.settings.yml
- Symlink for
sites/default/files
- Build steps for
boi_ci build:tests
- Deploy steps for
boi_ci deploy:git main
.gitlab-ci.yml
Provides CI steps for using GitLab CI.
settings.php
A Drupal settings file for environment-wide settings.
Steps to Deploy an Artifact
Create an SSH Key for Deployment Generate an SSH key pair for deployment using the following command:
ssh-keygen -t rsa -b 4096
Add the Private Key to GitLab
- Copy the private key and add it to GitLab as
DEPLOY_KEY
. - Ensure you include a new line after pasting the private key.
- Copy the private key and add it to GitLab as
Authorize the Public Key on the Deploy Host
- Copy the public key to the
~/.ssh/authorized_keys
file on the deploy host. - Alternatively, use a host-specific method to approve SSH authentication.
- Copy the public key to the
Set Up a Git Repository on the Host If not using a Git-based deployment provider, create a Git repository on the host:
touch README.md git init git add . git commit -m "Initial Commit" git config receive.denyCurrentBranch updateInstead
Update
.boi_ci.yml
Modify the.boi_ci.yml
file to include an environment path matching your Git repository, e.g.:/home/1250965.myhost.com/xxxx/public_html
Run the Build Using GitLab CI Trigger the build process using GitLab CI.
Verify the Deployment Confirm that the build succeeds and the files are deployed to the correct location.
Troubleshooting If the build fails because of changes to settings.php this is because of the executable permissions that get added. Make sure to set the same permissions on the file as will be set during an artifcat build.