Download the PHP package nrel/communications-project without Composer

On this page you can find all versions of the php package nrel/communications-project. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Informations about the package communications-project

This is a Composer-based installer for the Communications sub-profile based on the Lightning Drupal distribution. Welcome to the future!

Get Started

Composer will create a new directory called MY_PROJECT containing a directory with a full Lightning code base therein. You can then install it like you would any other Drupal site.

Maintenance

, , and their ilk are the old-school way of maintaining your code base. Forget them. You're in Composer land now!

Let this handy table be your guide:

Task Drush Composer
Installing a contrib project (latest version)
Installing a contrib project (specific version)
Updating all contrib projects and Drupal core
Updating a single contrib project
Updating Drupal core

The magic is that Composer, unlike Drush, is a dependency manager. If module depends on , Composer will not let you update baz to (or downgrade it to , for that matter). Drush has no concept of dependency management. If you've ever accidentally hosed a site because of dependency issues like this, you've probably already realized how valuable Composer can be.

But to be clear: it is still very helpful to use a site management tool like Drush or Drupal Console. Tasks such as database updates () are still firmly in the province of such utilities. This installer will install a copy of Drush (local to the project) in the directory.

Specifying a version

you can specify a version from the command line with:

$ composer require drupal/<modulename>:<version>

For example:

$ composer require drupal/ctools:3.0.0-alpha26
$ composer require drupal/token:1.x-dev

In these examples, the composer version 3.0.0-alpha26 maps to the drupal.org version 8.x-3.0-alpha26 and 1.x-dev maps to 8.x-1.x branch on drupal.org.

If you specify a branch, such as 1.x you must add -dev to the end of the version.

Composer is only responsible for maintaining the code base.

Source Control

If you peek at the we provide, you'll see that certain directories, including all directories containing contributed projects, are excluded from source control. This might be a bit disconcerting if you're newly arrived from Planet Drush, but in a Composer-based project like this one, you SHOULD NOT commit your installed dependencies to source control.

When you set up the project, Composer will create a file called , which is a list of which dependencies were installed, and in which versions. Commit to source control! Then, when your colleagues want to spin up their own copies of the project, all they'll have to do is run , which will install the correct versions of everything in .

All versions of communications-project with dependencies

PHP Build Version
Package Version
Requires drupal-composer/drupal-scaffold Version ^2.0.0
cweagans/composer-patches Version ^1.6.0
nrel/communications Version ^1.1.1.16
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package nrel/communications-project contains the following files

Loading the files please wait ....