Releases: forumone/generator-web-starter
v2.8.0
v2.7.3
- Dependency version updates
- Revise ESLint configuration to add Codacy scanning support
- Incorporate project generation support for Codacy for Drupal and
WordPress projects - Set the default web root directory name to web
- Revise testing pipeline sequence for steps
v2.7.3-alpha1
- Dependency version updates
- Revise ESLint configuration to add Codacy scanning support
- Incorporate project generation support for Codacy for Drupal and
WordPress projects
Release v2.7.2
- Dependency version bumps
- Containerized execution support
- Buildkite test scenario support
- Improved colorization of debug log outpu
v2.7.2-alpha1
Updates Introduced:
- [WSGEN-32] Implement Composer 2 support for projects
- [WSGEN-38] Reduce Drupal project generation to a single Composer
install operation instead of sequential updates and installs - [WSGEN-33] Remove prepare-for-pantheon Composer script from
Drupal Pantheon installations to correct missing gitignore
entries - Revise content of .dockerignore files
- Generate .gitignore and .dockerignore files from templates
- Add significantly more debugging output throughout installations
- [WSGEN-1] Fix formatting in composer.json files
- Add support for auth.json files in generated WordPress projects
Release v2.7.0
- [Security] Bump ini from 1.3.5 to 1.3.8
- Bump misc. dependency versions
- Set version for twig tweak to support Drupal 8
- Alpha: Manifest generator
- This functionality is known to need further work, but is ready for
testing and feedback.
- This functionality is known to need further work, but is ready for
- Alpha: Buildkite pipeline generator
- This functionality is known to need further work, but is ready for
testing and feedback.
- This functionality is known to need further work, but is ready for
Release v2.7.0-alpha1
This release is an updated rebuild of the previous functionality in v2.6.0-rc2 following the release of separate new features in the v2.6.0 release.
Testing Instructions
All sub-generator commands listed below assume usage of forumone/forumone-cli v1.7.0 or greater.
Generating a new project
f1 init --nextAs of right now, the new sub-generators generators are not incorporated into the primary project creation generator, so they will need to be executed separately using the commands below.
Generating the project manifest file
This generator will run through a series of prompts to gather overall project details and allow for configuration of:
- Git repositories
- Deployment environments
- Deployment workflows
f1 init --next --sub-generator=manifestGenerating a Buildkite pipeline.yml file
Generation of the pipeline.yml file and related dependencies may be executed using this generator, but an existing project manifest file is required from a previous execution of the manifest generator as instructed above.
f1 init --next --sub-generator=buildkite-pipelineRelease v2.6.0 - Elasticsearch Support
- Add generator support for elasticsearch
- Run the basic web-starter generator and select elasticsearch
- Revise multistage format of services/[drupal/wordpress]/Dockerfile
- Bump dependency versions
Release candidate v2.6.0-rc2
Add early draft of a code-quality generator that may be executed using:
npx -p yo -p generator-web-starter@next yo web-starter:code-qualityor if you're using the current pre-release of f1 cli:
f1 init --next --sub-generator=code-qualityTesting Instructions
All sub-generator commands listed below assume usage of forumone/forumone-cli v1.7.0 or greater.
Generating a new project
f1 init --nextAs of right now, the new sub-generators generators are not incorporated into the primary project creation generator, so they will need to be executed separately using the commands below.
Generating the project manifest file
This generator will run through a series of prompts to gather overall project details and allow for configuration of:
- Git repositories
- Deployment environments
- Deployment workflows
f1 init --next --sub-generator=manifestGenerating a Buildkite pipeline.yml file
Generation of the pipeline.yml file and related dependencies may be executed using this generator, but an existing project manifest file is required from a previous execution of the manifest generator as instructed above.
f1 init --next --sub-generator=buildkite-pipelineGenerating code-quality support
Most functionality within this generator is still being added and will be fleshed out further in the next release candidate.
At this time, the web-starter:code-quality sub-generator performs the following changes within a project:
- Add configuration for a new
code-qualityDocker Compose service withindocker-compose.cli.yml - Create a
robo.ymlfile for configuration of commands within upcoming code quality tools - Create a new
.envand.env.examplefile within the top-level directory of the project- The
.envfile is not intended to be committed to enable local customization - The values within the
.envfile beside thedocker-compose.*.ymlfiles are loaded for Docker Compose commands and may be interpolated into configuration within those files.
- The
f1 init --next --sub-generator=code-qualityRelease candidate v2.6.0-rc1
- Incorporate changes in release v2.5.2
- Remove Code Climate steps from generated pipeline.yml output
- Only ouput relevant release steps in pipeline.yml
See ongoing generator development in pull request #289
Testing Instructions
Generating a new project
f1 init --nextor
npx -p yo -p generator-web-starter@next yo web-starter
As of right now, the manifest and Buildkite pipeline generators are not incorporated into the project creation generator, so they will need to be executed separately using the commands below.
Generating the project manifest file
This generator will run through a series of prompts to gather overall project details and allow for configuration of:
- Git repositories
- Deployment environments
- Deployment workflows
npx -p yo -p generator-web-starter@next yo web-starter:manifestGenerating a Buildkite pipeline.yml file
Generation of the pipeline.yml file and related dependencies may be executed using this generator, but an existing project manifest file is required from a previous execution of the manifest generator as instructed above.
npx -p yo -p generator-web-starter@next yo web-starter:buildkite-pipeline