Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Fixes #1822 Update 02-libraries.md #1824

Merged
merged 1 commit into from

2 participants

@lrcg

Re #1823, if username is unrelated, then I propose username rather than composer or acme to avoid confusion.

@lrcg lrcg Fixes #1822 Update 02-libraries.md
If username is unrelated, then I propose `username` rather than `composer` or `acme` to avoid confusion.
fe88dee
@Seldaek Seldaek merged commit ed82543 into composer:master
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Apr 24, 2013
  1. @lrcg

    Fixes #1822 Update 02-libraries.md

    lrcg authored
    If username is unrelated, then I propose `username` rather than `composer` or `acme` to avoid confusion.
This page is out of date. Refresh to see the latest.
Showing with 2 additions and 2 deletions.
  1. +2 −2 doc/02-libraries.md
View
4 doc/02-libraries.md
@@ -122,7 +122,7 @@ the `.gitignore`.
Once you have a vcs repository (version control system, e.g. git) containing a
`composer.json` file, your library is already composer-installable. In this
example we will publish the `acme/hello-world` library on GitHub under
-`github.com/acme/hello-world`.
+`github.com/username/hello-world`.
Now, To test installing the `acme/hello-world` package, we create a new
project locally. We will call it `acme/blog`. This blog will depend on
@@ -150,7 +150,7 @@ We do this by adding a package repository specification to the blog's
"repositories": [
{
"type": "vcs",
- "url": "https://github.com/acme/hello-world"
+ "url": "https://github.com/username/hello-world"
}
],
"require": {
Something went wrong with that request. Please try again.