Remove obsolete ToC

Update composer recommendations
This commit is contained in:
Damian Mooyman 2017-10-25 12:04:04 +13:00
parent d56c756074
commit ebe20bb643
No known key found for this signature in database
GPG Key ID: 78B823A10DE27D1A

View File

@ -6,21 +6,6 @@ This version introduces many breaking changes, which in most projects can be man
of automatic upgrade processes as well as manual code review. This document reviews these changes and will
guide developers in preparing existing 3.x code for compatibility with 4.0
* [Overview](#overview)
* [Upgrading Guide](#upgrading)
* [Standard Upgrade](#upgrading-primary)
* [API Specific Upgrades](#upgrading-specifics)
* [User code style upgrades](#usercode-style-upgrades)
* [API Changes](#api-changes)
* [General and Core API](#overview-general)
* [ORM API](#overview-orm)
* [Filesystem API](#overview-filesystem)
* [Template and Form API](#overview-template)
* [i18n API](#overview-i18n)
* [Email and Mailer API](#overview-mailer)
* [SapphireTest API](#overview-testing)
* [Security API](#overview-security)
## <a name="overview"></a>Overview
* Minimum version dependencies have increased; PHP 5.5 and Internet Explorer 11 (or other modern browser)
@ -86,8 +71,7 @@ Backup your existing `composer.json` and overwrite it with the following content
{
"name": "myvendor/myproject",
"require": {
"silverstripe/recipe-plugin": ">=0.1@dev <1.0",
"silverstripe/recipe-cms": "~1.1"
"silverstripe/recipe-cms": "^1"
},
"prefer-stable": true,
"minimum-stability": "dev"
@ -103,6 +87,15 @@ Now run a `composer update`. This will remove all existing modules from your loc
since we replaced your project's `composer.json`. Now you can move back your modules
one by one, checking for compatible versions on [packagist.org](http://packagist.org).
Note: If you have issues with a pre-existing composer install you can force a clean re-install with the
below commands:
```bash
rm -rf vendor/composer
rm composer.lock
composer update
```
For modules with stable releases, simply set your composer constraints to the new version
(with a [next significant release](https://getcomposer.org/doc/articles/versions.md#next-significant-release-operators) operator).
@ -155,9 +148,18 @@ unless you PHP's built-in webserver through [silverstripe/serve](https://github.
The [upgrader tool](https://github.com/silverstripe/silverstripe-upgrader/) has a task runner which
automates this process for you.
Install the upgrader:
```
export PATH=$PATH:~/.composer/vendor/bin/
composer global require silverstripe/upgrader
```
Run the upgrader:
```
cd ~/my-project-root
~/.composer/vendor/bin/upgrade-code doctor
upgrade-code doctor
```
This will ensure that your `.htaccess` and `index.php` are set to a reasonable default value