amazeelabs/silverback

This package is abandoned and no longer maintained. The author suggests using the amazeelabs/silverback-cli package instead.

Scaffolder for Amazee Silverback projects.

8.9.1 2019-12-10 15:36 UTC

Requires

• alchemy/zippy: ^0.4.9
• cweagans/composer-patches: ^1.6.5
• drupal/admin_toolbar: ^2.0
• drupal/ckeditor5_sections: dev-1.x
• drupal/components: ^1.1
• drupal/console: ^1.0.2
• drupal/core: ^8.8.0
• drupal/cypress: ^1.0-alpha10
• drupal/delivery: dev-1.x
• drupal/entity_usage: ^2.0@alpha
• drupal/environment_indicator: ^3.0
• drupal/field_group: ^3.0@RC
• drupal/formdazzle: ^1.0
• drupal/graphql: ^3.0@RC
• drupal/graphql_twig: ^1.0@beta
• drupal/graphql_views: ^1.0@beta
• drupal/linkit: ^5.0@beta
• drupal/moderation_state_buttons_widget: dev-1.x
• drupal/moderation_state_columns: dev-1.x
• drupal/moderation_state_permissions: dev-1.x
• drupal/npm: dev-1.x
• drupal/redirect: ^1.2
• drupal/revision_tree: dev-1.x
• drupal/tmgmt: ^1.6
• drupal/token: ^1.5.0
• drupal/user_reference_access: dev-1.x
• drupal/webpack: dev-1.x
• drupal/webpack_babel: dev-1.x
• drupal/webpack_react: dev-1.x
• drush/drush: ^9.7.1 | ^10.0.0
• vlucas/phpdotenv: ^4.0
• wikimedia/composer-merge-plugin: ^1.4

GPL-2.0-or-later

• Philipp Melab<[e-mail]>

README

Amazee Silverback

amazee/silverback is a composer package adding common project dependencies, tooling and configuration scaffolding to Amazee Drupal projects. It aims to improve product quality and reduce maintenance costs by encouraging three simple principles:

1. Maximize open source: Lower initial costs, technical debt and maintenance costs by using and contributing to open source code as much as possible. For every feature required by a project that is not solvable by configuration or theming, try to find a generic solution that can be contributed and added as a dependency to amazeelabs/silverback.
2. Minimize requirements: It has to be as easy as possible to work on a project. If you need the production database and a local elasticsearch cluster to edit CSS files, you are doing microservices terribly wrong. Example: By default silverback development sites run on SQLite. MySQL is considered a performance optimization, and it's not in the projects scope to test Drupal's database abstraction layer.
3. Testability first: A project has to be fully testable with only the git repository at any time. All required assets (test content, media, configuration) have to be set up during the installation process. It must not rely on production data. Every feature and bug fix has to bring a test case that can be reproduced. It might take more time initially, but it will pay off.