Download the PHP package droath/drush-module-sync without Composer
On this page you can find all versions of the php package droath/drush-module-sync. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download droath/drush-module-sync
More information about droath/drush-module-sync
Files in droath/drush-module-sync
Package drush-module-sync
Short Description Sync Drupal modules based on a defined scope.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package drush-module-sync
Drush Module Sync
Sync Drupal modules based on a defined scope. Scopes are arbitrary but in most cases they're setup to match different environments, which are usually invoked based on different build processes that need to take place. The appropriate module(s) will be synced (installed/uninstalled) based on the scope definition that are defined in a YAML configuration.
Dependencies
- Drush
- Drupal 8
Similar Concept
- Master - Drupal 7
Getting Started
First, you'll need to download the drush-module-sync library using composer:
Next, you need to create a module-sync configuration file. This can be done by executing the following command:
Once invoked, the command will prompt for input as it generates your module-sync.yml configuration. When adding scopes I usually input both local and stage, as those are common environments that require different modules to be installed or uninstalled. By default the module-sync.yml file will be generated in the Drupal site path, which is usually path-to-drupal/sites/default if you're not using a multi-site configuration.
You can set the save path to a different directory, by providing the --path option.
Now you can edit the module-sync.yml configuration that was generated. You can define different modules for each scope modules directive:
As you can see the scope can extend from the base directive, as this is useful to remove module redundancy between multiple scopes. If you don't want to extend from the base, just set extend_base to false. Make sure to remove any modules from the base directive if you only want that module to be installed for a particular scope, which should already been defined.
Finally, after you've tweaked your module-sync configurations to your liking you can run the following command to execute the sync process.
Note: You can pass along the --yes|-y flag to confirm all prompts.
The command will evaluate what modules that have already been installed or need to be uninstalled for the given scope. Make sure you only run this command with the --yes flag when your certain all modules have been accounted for, as you could have undesired consequences.
