This workshop will be retired on May 1, 2025.

Heads up! To view this whole video, sign in with your Courses account or enroll in your free 7-day trial. Sign In Enroll

Dependency Management with Composer

Preview

Start a free Courses trial
to watch this video

Sign up for Treehouse

Finding and Using Packages

8:51 with Alena Holligan

Repositories are a central location where packages are stored. Composer uses Packagists for its' package repository. Most packages in the PHP community are in the Packagist repository. Packagist also contains many JavaScript Libraries as well.

Repositories

Packagist.org - Default package repository

Composer Documentation - The repository chapter of the documentation will explain the concept of packages and repositories, what kinds of repositories are available, and how they work.

Packages Used in this Video

CKEditor

ckeditor/ckeditor on packagist

What-You-See-Is-What-You-Get (W-Y-S-I-W-Y-G ) editors bring common word processor features directly to your web pages.

CKEditor is fully documented, including a Quick Start Guide for Adding CKEditor to your page.

HTML Purifier

HTML Purifier is a standards-compliant HTML filter library written in PHP. HTML Purifier will not only remove all malicious code (better known as XSS) with a thoroughly audited, secure yet permissive whitelist, it will also make sure your documents are standards compliant, something only achievable with a comprehensive knowledge of W3C's specifications.

ezyang/htmlpurifier on packagist

Related Discussions

Have questions about this video? Start a discussion with the community and Treehouse staff.

Sign up

    Related Discussions

    Have questions about this video? Start a discussion with the community and Treehouse staff.

    Sign up

    Each dependency that composer maintains is called a package. 0:00
    To utilize packages, they need to be accessible from somewhere. 0:05
    This location is called a repository. 0:09
    By default, composer uses packages dot org for its package repository. 0:12
    If you want to include packages that are not on packages 0:18
    such as your own private packages. 0:22
    You'll need to define a custom package repository. 0:24
    Check the notes associated to this video for more information. 0:28
    Most packages in the PHP community are in the packages repository. 0:32
    So this should only apply to very custom instances. 0:37
    Let's take a look at packages and see what we get. 0:40
    The home page gives us two ways to get started. 0:45
    Using packages with composer and publishing your own packages to packages. 0:48
    We can also browse packages. 0:53
    New releases, popular packages, and random packages, or we can search for a package. 0:57
    For example, let's search for phpmailer. 1:06
    Because composer uses packages as well, the results from this search are the same 1:11
    as the results we saw when we did a search using composer require. 1:16
    When we click on phpmailer, we can see a link to the GitHub repo on the right 1:21
    along with quite a bit of information pulled from GitHub. 1:25
    An important place to notice is a section in the middle 1:29
    that talks about how this package relates to other packages. 1:32
    As we saw an installation, there are no requirements but there are suggestions. 1:36
    Also shown is the development requirements and details such as conflicts and 1:41
    replacements. 1:45
    We can also check different versions by clicking on the version 1:47
    number on the right. 1:50
    I want to allow formatting for my emails, like bold, and adding links. 1:53
    To do this, let's use a what you see is what you get editor for text area. 1:57
    An easy WYSIWYG option that I like to use is CKEditor. 2:02
    Let's search for CKEditor. 2:07
    CKEditor is actually a JavaScript library. 2:16
    But this isn't a problem since composer can handle JavaScript libraries as well as 2:19
    PHP libraries. 2:24
    Let's go back into work spaces and add the CKEditor to our application. 2:25
    First, we use our console. 2:30
    And type composer require ckeditor/ckeditor. 2:34
    We can then run composer update ckeditor/ckeditor. 2:51
    This installed the package. 3:10
    Because this is a JavaScript library, 3:12
    our actual usage will change from how we use the PHP mailer. 3:14
    There are two steps to using the CKEditor on our site. 3:19
    Let's close the console. 3:23
    First, we need to call the CKEditor script using a script element on our page. 3:27
    Src='vendor/ckeditor/ckeditor, 3:39
    ckeditor.js. 3:51
    We can see that, if we refresh our file list. 3:57
    Ckeditor, ckeditor. 4:12
    And then ckeditor.js. 4:20
    The next step is to replace the existing text area element using JavaScript. 4:28
    CKEDITOR.replace('message'). 4:38
    Message is the name of the text area we wish to replace. 4:49
    Check the notes attached to this video for documentation on the CKEditor. 4:53
    Let's preview our application in the browser again. 4:58
    This time, we see an editor at the top of our text area which allows us to format 5:10
    the email message. 5:15
    If I'm going to allow formatting, I can't just filter input and 5:17
    sanitize the string because this will remove all the HTML tags. 5:20
    So what can we do to keep our HTML safe? 5:25
    Well, we could write our own script for testing and modifying input. 5:29
    But this could get complicated quickly, and 5:34
    we could easily overlook an important issue. 5:36
    Why spend our time coding something that already exists? 5:39
    Wouldn't it be better to spend our time creating something new? 5:42
    Google is a great place to research what's out there, and 5:46
    what other people are doing. 5:50
    If we search for something such as safe html filter with php, 5:52
    we'll find things such as the HTML purifier. 5:58
    If we click download and scroll down, we can see the example for using composer. 6:05
    Lets copy this and go back into work spaces. 6:15
    We'd run the composer require, and then we can run composer update. 6:31
    Now, let's go back to the HTML purifier documentation. 6:49
    We see the three basic lines we need to start using the HTML purifier. 6:56
    Since we already have auto loading set up on this page, 7:01
    let's ignore the first line and just grab the next two lines. 7:04
    We'll paste those directly above setting our message variable. 7:20
    We'll change the variable clean HTML to message. 7:23
    And instead of using dirty HTML, we can use our filter input. 7:29
    We wanna make sure we remove the filter sanitized string because we're 7:39
    going to have the HTML purifier handle that for us. 7:44
    Let's preview our app once more. 7:52
    This time, we'll add some HTML. 8:09
    We'll also go into the source and add some JavaScript which by default, 8:16
    the HTML purifier will not allow. 8:21
    After we submit the email, we can view our logged email and 8:30
    verify that the HTML formatting was preserved. 8:33
    But JavaScript was removed, no alert box. 8:37
    And if we view source, We can see that the JavaScript was not added. 8:41

    You need to sign up for Treehouse in order to download course files.

    Sign up

      You need to sign up for Treehouse in order to set up Workspace

      Sign up