Bixal / bixal-site-drupal

Bixal drupal site
https://www.bixal.com
0 stars 0 forks source link

Bixal.com

Remote

The remote environments are hosted in platform.sh. See the ./.platform directory and .platform.app.yaml file for the configuration.

Working with the local

The local environment is based on Drupal Env and the Drupal Env Lando packages.

Branching

Use the following naming for your git branches.

feature/BSD-[ISSUE_NO]-[LOWER_CASE_DESCRIPTION]

Example

feature/BSD-64-robo-validate

Commit style

BSD fixes #64: Fixed coding standards issues.

Also acceptable:

Example:

BSD closes #64: Fixed coding standards issues.

More guidance on git branches and commit style in robo.yml

Starting the Environment

First time:

./robo.sh lando:init

For subsequent starts, you can just:

lando start

Change something in the .lando.yml config and/or you want to re-install front and back end dependencies?

lando rebuild -y

Re-install front and back end dependencies

lando build

Installing Drupal

lando si

This will install all the sample content we have created in web/modules/custom/bixal_default_content. In order to export new content here, create it locally and run lando export-content.

Running Drush

./drush.sh <your command>

Running Composer

./composer.sh

Using it this way allows you to use your local to run the composer command instead of Docker which often times out when using docker. To use your local composer:

Composer.log

There is a composer.log that is modified everytime you do something that changes the composer.lock file. It's important that you always use lando composer or ./composer.sh instead of plain composer to run composer commands. Otherwise, an entry in composer.log will not be made.

Access story book

Storybook preview is available here →

Storybook for this project can be found by:

Handy Commands for Development

Configure Xdebug

https://github.com/mattsqd/drupal-env-lando/wiki/XDebug-(Personal)