-
Notifications
You must be signed in to change notification settings - Fork 1
Backends customization workflow
- Custom Drupal modules can be added under
backend-donations
andbackend-gifts
services. - Custom Drupal modules must be added under
web/modules/custom/
directory of backend services.
- Go to project's root directory.
- Run
docker-compose exec be_donations ./vendor/bin/drupal generate:module --module-path="modules/custom"
and follow the interactive prompt.
Go to project's root directory.
Run docker-compose exec be_gifts ./vendor/bin/drupal generate:module --module-path="modules/custom"
and follow the interactive prompt.
Drupal console documentation can be checked here
Needs to be defined
Falcon related modules reside in modules/falcon
directory and developer must never edit and customize code in it. All Falcon related modules provide (should be providing) standard Drupal API ways of overriding existing functionality, logic or features.
- Find the piece of code you would like to alter under
modules/falcon
directory. - Identify how it is implemented and find relevant ways to override/alter the implementation.
- Create new or edit existing custom Drupal module under
modules/custom
directory to override and implement your custom implementation of existing Falcon code.
Also there are many ways to override existing Drupal module implementations, here is short list of common APIs used to override different parts of the system:
- Altering existing services, providing dynamic services
- Altering existing routes and adding new routes based on dynamic ones
- Hooks API
All Falcon based projects might have different configurations and in order to manage those configurations and prevent conflicting with Falcon's default configuration all developers should use config_split module. Config split module gives us ability to define custom/project specific configurations and export/import them safely.