silverstripe-installer/composer.json

{
	"name": "silverstripe/installer",
	"description": "The SilverStripe Framework Installer",
	"require": {
		"php": ">=5.3.2",
		"silverstripe/cms": "self.version",
		"silverstripe/framework": "self.version",
		"silverstripe-themes/simple": "*"
	},
	"config": {
		"process-timeout": 600	
	},
	"scripts": {
		"post-install-cmd": "php ./framework/cli-script.php dev/build",
		"post-update-cmd": "php ./framework/cli-script.php dev/build"
	},
	"minimum-stability": "dev"
}
Added composer.json Once we've sorted out packagist listing ownership, we should be able to remove the custom repository entries. 2012-11-01 17:26:18 +01:00			`{`
			`"name": "silverstripe/installer",`
			`"description": "The SilverStripe Framework Installer",`
			`"require": {`
			`"php": ">=5.3.2",`
FIX: Put self.version in composer dependencies. Now that https://github.com/composer/composer/pull/1883 is in Composer, self.version will work as a requirement for framework & cms. This will simplify the release process a great deal. Ultimately, the release of rc1 will be the place to test that, but it seems appropriate to get this in there for that. If it succeeds with 3.1-rc1, I'd suggest we backport to 3.0 and 2.4. 2013-05-13 11:07:57 +02:00			`"silverstripe/cms": "self.version",`
			`"silverstripe/framework": "self.version",`
Added composer.json Once we've sorted out packagist listing ownership, we should be able to remove the custom repository entries. 2012-11-01 17:26:18 +01:00			`"silverstripe-themes/simple": "*"`
			`},`
Include a higher timeout value to avoid timeouts. Checking out framework can often take longer than the default (300 seconds). This gives a 10min limit to creating a new project. 2013-03-06 08:22:48 +01:00			`"config": {`
			`"process-timeout": 600`
			`},`
NEW: Added post-install and post-update dev/build call. With this change, composer will automatically call dev/build after an update or install command. The main reason that this is 3.1-only is that previous releases would have necessitated the use of 'sudo -u www-data', which is too environment-specific. One thing that this may cause problems with is 'composer create-project' in an environment without a _ss_environment file. It will call dev/build, and dev/build will throw an error. That should be fixed in a subsequent commit. 2013-05-30 06:23:29 +02:00			`"scripts": {`
			`"post-install-cmd": "php ./framework/cli-script.php dev/build",`
			`"post-update-cmd": "php ./framework/cli-script.php dev/build"`
			`},`
Added composer.json Once we've sorted out packagist listing ownership, we should be able to remove the custom repository entries. 2012-11-01 17:26:18 +01:00			`"minimum-stability": "dev"`
NEW: Added dev dependencies to composer. FIX: Don't hardcode framework and cms version in installer. 2012-11-04 09:24:59 +01:00			`}`