Download the PHP package metadrop/drupal-updater without Composer
On this page you can find all versions of the php package metadrop/drupal-updater. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 drupal-updater
Drupal updater
Drupal updater helps you to update the drupal modules of your site.
It does an update of all your drupal modules and dependencies defined in the composer.json.
It also allows update only securities.
Requirements
This package works with:
- Drush >=10.
- Composer 2.4 (global).
Or alternatively, you can run it inside tools like ddev.
Installation
Before doing the installation, make sure your environment has composer 2.4 or higher installed locally.
Or, if you are using ddev:
How it works
This module will try to update your dependencies based on how they are required in the composer.json.
- Before starting to update, all the Drupal configuration is consolidated and commited into GIT.
- For each module / package updated the changes are commited:
- For PHP packages, it commits the composer.lock
- For Drupal extensions, it applies the updates, commits the configuration changed and the modified files. On multisites environments it will export/commit the configuration for all environments keeping them all synchronized (see parameters).
If a package has an available update and that update can't be done by running composer update, it won't do the upgrade. This means that not all packages will be upgraded, but most of them yes.
Usage
Basic update:
Parameters allowed:
- --security: It will update only securities.
- --no-dev: It won't update dev dependencies, only the primary ones.
- --author: It sets the git commits author. Example:
Test<[email protected]> - --environment: List of sites (drush alias) to be run on Drupal Multisites. The drush alias must be local.
Examples:
-
Update securities:
-
Update only primary packages:
-
Update specific packages:
-
Update with a specific author:
- Update on multiple sites (Drupal Multisite):
DDEV
If you are using ddev, you can just run the commands above prepending ddev exec.
Example:
All versions of drupal-updater with dependencies
symfony/process Version >=4
drush/drush Version >=10
davidrjonas/composer-lock-diff Version ^1.7