mirror of
https://github.com/silverstripe/silverstripe-framework
synced 2024-10-22 14:05:37 +02:00
306 lines
16 KiB
Markdown
306 lines
16 KiB
Markdown
# Installing and Upgrading with Composer
|
|
|
|
<div markdown='1' style="float: right; margin-left: 20px">
|
|
|
|
</div>
|
|
|
|
Composer is a package management tool for PHP that lets you install and upgrade SilverStripe and its modules. Although installing Composer is one extra step, it will give you much more flexibility than just downloading the file from silverstripe.org. This is our recommended way of downloading SilverStripe and managing your code.
|
|
|
|
For more information about Composer, visit [its website](http://getcomposer.org/).
|
|
We also have separate instructions for [installing modules with Composer](/topics/modules).
|
|
|
|
# Basic usage
|
|
|
|
## Installing composer
|
|
|
|
To install Composer, run the following commands from your command-line.
|
|
|
|
# Download composer.phar
|
|
curl -s https://getcomposer.org/installer | php
|
|
|
|
# Move to your path
|
|
sudo mv composer.phar /usr/local/bin/composer
|
|
|
|
Or [download composer.phar](http://getcomposer.org/composer.phar) manually, and rename `composer.phar` as `composer`, and put it in your path. On Windows, you should call the file `composer.bat`.
|
|
|
|
You can then run Composer commands by calling `composer`. For example:
|
|
|
|
composer help
|
|
|
|
<div class="hint" markdown="1">
|
|
It is also possible to keep `composer.phar` out of your path, for example, to put it in your project root. Every command would then start with `php composer.phar` instead of `composer`. This is handy if need to keep your installation isolated from the rest of your computer's set-up, but we recommend putting composer into the path for most people.
|
|
</div>
|
|
|
|
#### Updating composer
|
|
|
|
If you already have composer installed you can update it by running:
|
|
|
|
sudo composer self-update
|
|
|
|
Composer updates regularly, so you should run this command fairly often. These instructions assume you are running the latest version.
|
|
|
|
## Create a new site
|
|
|
|
Composer can create a new site for you, using the installer as a template:
|
|
|
|
composer create-project silverstripe/installer ./my/website/folder
|
|
|
|
`./my/website/folder` should be the root directory where your site will live.
|
|
For example, on OS X, you might use a subdirectory of `~/Sites`.
|
|
As long as your web server is up and running, this will get all the code that you need.
|
|
Now visit the site in your web browser, and the installation process will be completed.
|
|
|
|
By default composer will download the latest stable version. You can also specify
|
|
a version to download that version explicitly, i.e. this will download the older `3.0.3` release:
|
|
|
|
composer create-project silverstripe/installer ./my/website/folder 3.0.3
|
|
|
|
When `create-project` is used with a release version like above,
|
|
it will try to get the code from archives instead of creating
|
|
git repositories. If you're planning to contribute to SilverStripe,
|
|
see [Using development versions](#using-development-versions).
|
|
|
|
## Adding modules to your project
|
|
|
|
Composer isn't only used to download SilverStripe CMS, it can also be used to manage all SilverStripe modules. Installing a module can be done with the following command:
|
|
|
|
composer require silverstripe/forum:*
|
|
|
|
This command has two parts. First is `silverstripe/forum`. This is the name of the package. You can find other packages with the following command:
|
|
|
|
composer search silverstripe
|
|
|
|
This will return a list of package names of the forum `vendor/package`. If you prefer, you can search for pacakges on [packagist.org](https://packagist.org/search/?q=silverstripe).
|
|
|
|
The second part after the colon, `*`, is a version string. `*` is a good default: it will give you the latest version that works with the other modules you have installed. Alternatively, you can specificy a specific version, or a constraint such as `>=3.0`. For more information, read the [Composer documentation](http://getcomposer.org/doc/01-basic-usage.md#the-require-key).
|
|
|
|
<div class="warning" markdown="1">
|
|
`master` is not a legal version string - it's a branch name. These are different things. The version string that would get you the branch is `dev-master`. The version string that would get you a numeric branch is a little different. The version string for the `3.0` branch is `3.0.x-dev`.
|
|
</div>
|
|
|
|
## Updating dependencies
|
|
|
|
Except for the control code of the Voyager space probe, every piece of code in the universe gets updated from time to time. SilverStripe modules are no exception.
|
|
|
|
To get the latest updates of the modules in your project, run this command:
|
|
|
|
composer update
|
|
|
|
Updates to the required modules will be installed, and the `composer.lock` file will get updated with the specific commits of each of those.
|
|
|
|
## Deploying projects with Composer
|
|
|
|
When deploying projects with composer, you could just push the code and run `composer update`. However, this is risky. In particular, if you were referencing development dependencies and a change was made between your testing and your depoyment to production, you would end up deploying untested code. Not cool!
|
|
|
|
The `composer.lock` file helps with this. It references the specific commits that have been checked out, rather than the version string. You can run `composer install` to install dependencies from this rather than `composer.json`.
|
|
|
|
So, your deployment process, as it relates to Composer, should be as follows:
|
|
|
|
* Run `composer update` on your development version before you start whatever testing you have planned. Perform all the necessary testing.
|
|
* Check `composer.lock` into your repository.
|
|
* Deploy your project code base, using the deployment tool of your choice.
|
|
* Run `composer install` on your production version.
|
|
|
|
# Dev Environments for Contributing Code {#contributing}
|
|
|
|
So you want to contribute to SilverStripe? Fantastic! You can do this with composer too.
|
|
You have to tell composer three things in order to be able to do this:
|
|
|
|
- Keep the full git repository information
|
|
- Include dependancies marked as "developer" requirements
|
|
- Use the development version, not the latest stable version
|
|
|
|
The first two steps are done as part of the initial create project using additional arguments.
|
|
|
|
|
|
composer create-project --keep-vcs --dev silverstripe/installer ./my/website/folder 3.0.x-dev
|
|
|
|
The process will take a bit longer, since all modules are checked out as full git repositories which you can work on. The command checks out from the 3.0 release line. To check out from master instead,
|
|
replace `3.0.x-dev` with `dev-master` (more info on [composer version naming](http://getcomposer.org/doc/02-libraries.md#specifying-the-version)).
|
|
|
|
The `--keep-vcs` flag will make sure you have access to the git history of the installer and the requirements
|
|
|
|
The `--dev` flag is optional, and can be used to add a couple modules which are useful for
|
|
SilverStripe development:
|
|
|
|
* The `behat-extension` module allows running [Behat](http://behat.org) integration tests
|
|
* The `docsviewer` module will let you preview changes to the project documentation
|
|
* The `buildtools` module which adds [phing](http://phing.info) tasks for creating SilverStripe releases
|
|
|
|
Once the `create-project` command completes, you need to edit the `composer.json` in the project root
|
|
and remove the `@stable` markers from the `silverstripe/cms` and `silverstripe/framework` version entries.
|
|
Another `composer update --dev` call will now fetch from the development branch instead.
|
|
Note that you can also convert an existing composer project with these steps.
|
|
|
|
Please read the ["Contributing Code"](/misc/contributing/code) documentation to find out how to
|
|
create forks and send pull requests.
|
|
|
|
# Advanced usage
|
|
|
|
## Manually editing composer.json
|
|
|
|
To remove dependencies, or if you prefer seeing all your dependencies in a text file, you can edit the `composer.json` file. It will appear in your project root, and by default, it will look something like this:
|
|
|
|
{
|
|
"name": "silverstripe/installer",
|
|
"description": "The SilverStripe Framework Installer",
|
|
"require": {
|
|
"php": ">=5.3.2",
|
|
"silverstripe/cms": "3.0.*",
|
|
"silverstripe/framework": "3.0.*",
|
|
"silverstripe-themes/simple": "*"
|
|
},
|
|
"require-dev": {
|
|
"silverstripe/compass": "*",
|
|
"silverstripe/docsviewer": "*"
|
|
},
|
|
"minimum-stability": "dev"
|
|
}
|
|
|
|
To add modules, you should add more entries into the `"require"` section. For example, we might add the blog and forum modules. Be careful with the commas at the end of the lines!
|
|
|
|
Save your file, and then run the following command to refresh the installed packages:
|
|
|
|
composer update
|
|
|
|
## Using development versions
|
|
|
|
Composer will by default download the latest stable version of silverstripe/installer.
|
|
The `composer.json` file that comes with silverstripe/installer may also explicitly state it requires the stable version of cms and framework - this is to ensure that when developers are getting started, running `composer update` won't upgrade their project to an unstable version
|
|
|
|
However it is relatively easy to tell composer to use development versions. Not only
|
|
is this required if you want to contribute back to the SilverStripe project, it also allows you to get fixes and API changes early.
|
|
|
|
This is a two step process. First you get composer to start a project based on
|
|
the latest unstable silverstripe/installer
|
|
|
|
composer create-project silverstripe/installer ./my/website/folder master-dev
|
|
|
|
Or for the latest development version in the 3.0.x series
|
|
|
|
composer create-project silverstripe/installer ./my/website/folder 3.0.x-dev
|
|
|
|
## Working with project forks and unreleased modules
|
|
|
|
By default, Composer will install modules listed on the packagist site. There a few reasons that you might not
|
|
want to do this. For example:
|
|
|
|
* You may have your own fork of a module, either specific to a project, or because you are working on a pull request
|
|
* You may have a module that hasn't been released to the public.
|
|
|
|
There are many ways that you can address this, but this is one that we recommend, because it minimises the changes you would need to make to switch to an official version in the future.
|
|
|
|
This is how you do it:
|
|
|
|
* **Ensure that all of your fork repositories have correct composer.json files.** Set up the project forks as you would a distributed package. If you have cloned a repository that already has a composer.json file, then there's nothing you need to do, but if not, you will need to create one yourself.
|
|
|
|
* **List all your fork repositories in your project's composer.json files.** You do this in a `repositories` section. Set the `type` to `vcs`, and `url` to the URL of the repository. The result will look something like this:
|
|
|
|
{
|
|
"name": "silverstripe/installer",
|
|
"description": "The SilverStripe Framework Installer",
|
|
|
|
"repositories": [
|
|
{
|
|
"type": "vcs",
|
|
"url": "git@github.com:sminnee/silverstripe-cms.git"
|
|
}
|
|
],
|
|
...
|
|
}
|
|
|
|
* **Install the module as you would normally.** Use the regular composer function - there are no special flags to use a fork. Your fork will be used in place of the package version.
|
|
|
|
composer require silverstripe/cms
|
|
|
|
Composer will scan all of the repositories you list, collect meta-data about the packages within them, and use them in favour of the packages listed on packagist. To switch back to using the mainline version of the package, just remove your the `repositories` section from `composer.json` and run `composer update`.
|
|
|
|
Now add an "upstream" remote to the original repository location so you can rebase or merge your fork as required.
|
|
|
|
cd advancedworkflow
|
|
git remote add -f upstream git://github.com/silverstripe/silverstripe-cms.git
|
|
|
|
For more information, read the ["Repositories" chapter of the Composer documentation](http://getcomposer.org/doc/05-repositories.md).
|
|
|
|
### Forks and branch names
|
|
|
|
Generally, you should keep using the same pattern of branch names as the main repositories does. If your version is a fork of 3.0, then call the branch `3.0`, not `3.0-myproj` or `myproj`. Otherwise, the depenency resolution gets confused.
|
|
|
|
Sometimes, however, this isn't feasible. For example, you might have a number of project forks stored in a single repository, such as your personal github fork of a project. Or you might be testing/developing a feature branch. Or it might just be confusing to other team members to call the branch of your modified version `3.0`.
|
|
|
|
In this case, you need to use Composer's aliasing feature to specify how you want the project branch to be treated, when it comes to dependency resolution.
|
|
|
|
Open `composer.json`, and find the module's `require`. Then put `as (core version name)` on the end.
|
|
|
|
{
|
|
...
|
|
"require": {
|
|
"php": ">=5.3.2",
|
|
"silverstripe/cms": "3.0.2.1",
|
|
"silverstripe/framework": "dev-myproj as 3.0.x-dev",
|
|
"silverstripe-themes/simple": "*"
|
|
},
|
|
...
|
|
}
|
|
|
|
What this means is that when the `myproj` branch is checked out into a project, this will satisfy any dependencies that 3.0.x-dev would meet. So, if another module has `"silverstripe/framework": ">=3.0.0"` in its dependency list, it won't get a conflict.
|
|
|
|
Both the version and the alias are specified as Composer versions, not branch names. For the relationship between branch/tag names and Composer vesrions, read [the relevant Composer documentation](http://getcomposer.org/doc/02-libraries.md#specifying-the-version).
|
|
|
|
This is not the only way to set things up in Composer. For more information on this topic, read the ["Aliases" chapter of the Composer documentation](http://getcomposer.org/doc/articles/aliases.md).
|
|
|
|
## FAQ
|
|
|
|
### How do I convert an existing module to using Composer?
|
|
|
|
Simply decide on a [unique name and vendor prefix](https://packagist.org/about),
|
|
create a `composer.json`, and either commit it or send a pull request to the module author.
|
|
Look at existing modules like the ["blog" module](https://github.com/silverstripe/silverstripe-blog/blob/master/composer.json) for good examples on what this file should contain.
|
|
It's important that the file contains a custom "type" to declare it as a
|
|
`silverstripe-module` or `silverstripe-theme` (see [custom installers](http://getcomposer.org/doc/articles/custom-installers.md)).
|
|
Then register the module on [packagist.org](http://packagist.org).
|
|
|
|
### How should I name my module?
|
|
|
|
Follow the packagist.org advice on choosing a [unique name and vendor prefix](https://packagist.org/about). Please don't use the `silverstripe/<modulename>` vendor prefix, since that's reserved
|
|
for modules produced by SilverStripe Ltd. In order to declare that your module is
|
|
in fact a SilverStripe module, use the "silverstripe" tag in the composer.json file,
|
|
and set the "type" to "silverstripe-module".
|
|
|
|
### What about themes?
|
|
|
|
Themes are technically just "modules" which are placed in the `themes/` subdirectory.
|
|
We denote a special type for them in the `composer.json` (`"type": "silverstripe-theme"`),
|
|
which triggers their installation into the correct path.
|
|
|
|
### How do I convert an existing project to Composer?
|
|
|
|
The easiest way is to follow the [upgrading](/installation/upgrading) instructions
|
|
and switch to a newer release. Alternatively, copy the `composer.json` file from
|
|
a newer release, and adjust the version settings in the "require" section to your needs.
|
|
You'll also need to update your webserver configuration
|
|
from there (`.htaccess` or `web.config` files), in order to prevent
|
|
web access to the composer-generated files.
|
|
|
|
### Do I need composer on my live server?
|
|
|
|
It depends on your deployment process. If you copy or rsync files to your live server,
|
|
the process stays the same. If the live server hosts a git repository checkout,
|
|
which is updated to push a newer version, you'll also need to run `composer install` afterwards.
|
|
We recommend looking into [Composer "lock" files](http://getcomposer.org/doc/01-basic-usage.md#composer-lock-the-lock-file) for this purpose.
|
|
|
|
### Can I keep using Downloads, Subversion Externals or Git Submodules?
|
|
|
|
Yes and no. Composer comes with additional features such as
|
|
[autoloading](http://getcomposer.org/doc/01-basic-usage.md#autoloading)
|
|
or [scripts](http://getcomposer.org/doc/articles/scripts.md)
|
|
which some modules will start relying on.
|
|
Please check the module README for specific installation instructions.
|
|
|
|
### I don't want to get development versions of everything!
|
|
|
|
You don't have to, Composer is designed to work on the constraints you set.
|
|
You can declare the ["minimum-stability"](http://getcomposer.org/doc/04-schema.md#minimum-stability)
|
|
on your project as suitable, or even whitelist specific modules as tracking
|
|
a development branch while keeping others to their stable release.
|
|
Read up on [Composer "lock" files](http://getcomposer.org/doc/01-basic-usage.md#composer-lock-the-lock-file) on how this all fits together. |