Composer update drupal code#
A library is basically a set of code that can be re-used by other sites. However, other developers have written code that handles OAuth 2 integration, and they have released this code on the internet in the form of a library.
Writing OAuth 2 integrations is tricky, as the authentication process is somewhat complex. This is a secure protocol that allows sites or applications to authenticate with other sites, such as Facebook, Google, Twitter, Instagram, and countless others. For example, the current standard for authentication (aka logging in) to remote systems is the OAuth 2 protocol. DRY is another way of saying don’t re-invent the wheel if someone else has already written code that does what you want to do, rather than writing code that does the same thing, it’s better to re-use the code that that has already been written. Traditionally, this referred to code within the codebase of a single application, but with Composer, code can now be shared between applications as well. This means that whenever possible, code should be re-used, rather than re-written. Programmers like to use the term DRY - Don’t Repeat Yourself. So let’s break it down a little further to understand what it means. That’s an accurate description, though a little wordy.
Composer update drupal software#
The Wikipedia page ( (software)) describes Composer as follows:Ĭomposer is an application-level package manager for the PHP programming language that provides a standard format for managing dependencies of PHP software and required libraries. So without further ado, let’s get started.
This is the first post in an explorative series of blog posts on Drupal and Composer, hopefully clearing up some of the confusion. This can be daunting for those without previous experience working with the command line, and can still be a confusing experience for those who do.
As any developer working with Drupal 8 knows, working with Composer has become an integral part of working with Drupal.
0 kommentar(er)
