Talk:Composer

further plans
There are many extensions witch helps to put extensions dependency under control (like Extension:Wiki Administration Tool). Is there a purpose to use composer instead or as a base? Exbe (talk) 21:41, 4 January 2013 (UTC)

Extension Configuration
Many extensions rely on or benefit from configuration. How is this accomplished with Composer? —The preceding unsigned comment was added by 76.107.83.121 (talk • contribs) 18:23, 15 December 2013 (UTC)
 * I'm wondering the same. --Nemo 13:15, 1 January 2014 (UTC)
 * Well, I think this is not the focus of Composer, so configuration will always have to be done in LocalSettings.php, except for the extensions invocation since they get autoloaded once installed. --&#91;&#91;kgh&#93;&#93; (talk) 17:30, 9 January 2014 (UTC)

No shell access
Looks like a great step forward (congrats!), but how do we run this on a shared host? Cavila (MW 1.19.7, MySQL 5.1.72-2, Php 5.3.3-7, SMW 1.8.0.5, SF 2.5.2) 16:24, 16 December 2013 (UTC)
 * My question has been answered elsewhere. You can't install this without shell access. Cavila (MW 1.22, MySQL 5.1.72-2, Php 5.3.3-7 squeeze, SMW 1.9.0.1, SF 2.6.1) 17:23, 8 January 2014 (UTC)
 * Obviously, you can use Composer to install things locally and just copy everything over to the server. --Nikerabbit (talk) 18:20, 8 January 2014 (UTC)
 * Well, but the question remain. I really love composer where I have access to the shell, but some extensions must be installe with composer, and where you have not the shell you are in trouble. How overcome this issue? --Gborgonovo (talk) 21:24, 8 March 2014 (UTC)

Uninstall?
How does one uninstall an extension that was installed using Composer? —The preceding unsigned comment was added by Lsilverman (talk • contribs) 22:00, 17 December 2013 (UTC)


 * I guess you first have to remove the extension from composer.json and then remove it from LocalSettings.php. Maybe there is a command like ? I've never used that software. Perhaps you only have to remove the extension from composer.json and run   afterwards, but I guess the frist solution is the proper one.  Tim (SVG)  15:07, 1 January 2014 (UTC)


 * I tried above, but was unsuccessful. I'm not able to identify to what file Composer "installs" the extension, but it doesn't appear to be localsettings.php.  Any guidance on this would be helpful--in fact, I think that if more and more extensions are going to be using Composer as a requirement), then uninstall instructions are essential Patelmm79 (talk) 16:14, 31 January 2014 (UTC)


 * Just had to uninstall an extension myself and the above worked for me: after removing the entry from composer.json I just hit . Since composer extensions are not loaded via LocalSettings.php, one does not need to edit it. -- Tobi (talk) 08:24, 5 March 2014 (UTC)