General information

For running new project for local development, you need to do the following steps:

1. Have or create docker network docker network create web
2. Have already started global traefik (you can use configured example https://bitbucket.org/dimando/ci_traefik/src)
3. Run task up
4. Run task install

Desired infrastructure state:

• Have a separate pipeline for the "master" branch on the production server.
• For all other branch names (including stage, dev, etc.), use the default pipeline with auto-creating environments according to the branch name on the dev-server.

Taskfile:

We use Task to run commands. You can find the task file in the root of the project.

• If you use zsh : https://github.com/sawadashota/go-task-completions.

• For PHPStorm : https://plugins.jetbrains.com/plugin/17058-taskfile.

• Use --force flag to force run task even if it's skipped by preconditions (example: Task "install" is up to date):

  task install --force.

During CI-CD process, we also use tha global Taskfile located in the /dimando/ folder. Sources of the global Taskfile: https://bitbucket.org/dimando/taskfile/.

For getting help on the available commands, run task --list. Feel free to adopt it for particular needs.

Dev environments setup steps:

1. Go to /admin/access-tokens in Bitbucket admin area for the project and add access token. The name could be anything. Then go to /admin/pipelines/repository-variables in Bitbucket admin area and add BITBUCKET_TOKEN variable with created token value.
2. Enable pipelines /admin/addon/admin/pipelines/settings in bitbucket admin area.
3. Make sure that you have configured runner for your new environment server (https://bitbucket.org/dimando/ansible/src/master/readme.md)

For MacOS users:

During task install you'll get darwin-specific variant of composer.override.yml file and .env.local.overrides file. Check /scripts/Taskfiles/Helpers for more info.