Drupal 7 NES Contrib Modules
Download and install NES versions of contributed Drupal 7 modules
Installation Methods
HeroDevs currently offers multiple methods to download and install Drupal 7 NES Contrib Modules:
If you need a different installation method, please contact support@herodevs.com.
Composer Installation
Authentication Setup
Create an auth.json
file or update your existing one:
{
"bearer": {
"registry.nes.herodevs.com": "<nes-access-token>"
}
}
Please contact support@herodevs.com if you don't have your access token.
This file contains sensitive credentials and should be excluded from source control.
Repository Configuration
Add the HeroDevs repository to your composer.json
file:
"repositories": [
{
"type": "composer",
"url": "https://registry.nes.herodevs.com/composer/repository"
}
]
Place this entry before packages.drupal.org
to ensure proper precedence.
Package Installation
First, add the NES Drupal module to your composer.json file:
composer require "neverendingsupport/<module-name-and-version>" --no-update
Then install dependencies:
composer update drupal/<module-name> --with-dependencies --no-dev
Direct Download and Manual Installation
Contact support@herodevs.com to receive your download URL.
Download through your browser using Basic Authentication, or use command line tools like cURL by setting authentication headers.
Download Package
Use cURL to download the tarball with your access token:
Please contact support@herodevs.com if you don't have your access token.
NES_ACCESS_TOKEN=[YOUR NES ACCESS TOKEN]
curl --header "Authorization: Bearer $NES_ACCESS_TOKEN" --output ./<module-name>.zip \
--location https://registry.nes.herodevs.com/composer/pkg/neverendingsupport/<module-name>/<version>/release.zip
Remove existing module from the contrib folder
It is recommended that you place your site in maintenance mode temporarily before replacing any modules with the HeroDevs NES version.
It is recommended that you use version control such as Git and test all changes in a development environment before making changes to your production site.
rm -rf /path/to/site/sites/all/modules/contrib/<module-name>
Unzip and move to correct folder
From the folder you downloaded the tarball to run:
unzip <module-name>.zip -d /path/to/site/sites/all/modules/contrib/<module-name>
Verify that the module has been uncompressed in the correct location.
Cleanup
Remove the downloaded zip file from your root directory.
Clear caches with:
drush cc all