contao-community-alliance/composer-installer

This package is abandoned and no longer maintained. The author suggests using the contao-community-alliance/composer-plugin package instead.

1.7.1 2013-11-26 19:34 UTC

Requires

• contao/core: >=2.11,<3.3

Conflicts

• contao-community-alliance/composer: <0.7.10
• contao/core: 3.0.*

LGPLv3

README

contao composer installer

Symlinks

Contao require a strict module structure. Composer install all dependencies into the vendor directory, using the complete repository structure. Both often not match each other.

To solve this problem, without making a lot of shadow copies the contao-module installer create symlinks.

Hint for users: Symlinks require a good server setup. To work with Apache2 the FollowSymLinks option is mostly required.

Hint for developers: PHP will follow symlinks by default, but using __DIR__ or __FILE__ will return the real path. You will get composer/vendor/me/my-module/MyClass.php instead of system/modules/my-module/MyClass.php.

Hint for Windows users: Symlinks on Windows require PHP 5.3+, but this is no real problem, because composer require PHP 5.3+ ;-)

Installing repository root as module my-module: Hint: This is the implicit fallback (system/modules/$packageName), if no symlinks specified!

{
	"extra": {
		"symlinks": {
			"": "system/modules/my-module"
		}
	}
}

Installing repository sub-path src/system/modules/my-module as module my-module:

{
	"extra": {
		"symlinks": {
			"src/system/modules/my-module": "system/modules/my-module"
		}
	}
}

Userfiles

Sometimes you need to provide user files (files within the (tl_)files directory). There is a support to install these user files. Normally these files can be modified by users. To protect user changes, user files are only copied if they are not exists. The installer will never overwrite a user file.

Hint: User files are installed into the $uploadPath directory, not TL_ROOT.

{
	"extra": {
		"userfiles": {
			"src/system/modules/my-module/files/images": "my-module/images"
		}
	}
}

Runonces

Putting your runonce.php into your modules config directory is not a good idea in combination with composer. After contao runs the runonce.php it get deleted. Next time you do an update, composer complains about this modification. To solve this, you can define your runcone.php's, yes you are right, you can use multiple runonce.php files. There is no need to name them runonce.php, feel free to use any other name.

{
	"extra": {
		"runonce": [
			"src/system/modules/my-module/runonce/init_update.php",
			"src/system/modules/my-module/runonce/do_db_update.php",
			"src/system/modules/my-module/runonce/refresh_entities.php"
		]
	}
}

Hint: The order of the runonce files is taken into account.

Hint: No, the installer will not support directories. This is just to protect unexpected behavior.