Re: [oxid-dev-general] Using Composer

[Theodorus Bruchwald | superReal GmbH]

Hi Alexander, we have just integrated some our modules and externals libraries into EE 4.6.x using composer. We would like to get the opportunity to show our experiences with Composer on OXID Commons 2013 ;) Best regards, Theodorus Bruchwald ---------------------------- superReal GmbH Create Commerce ---------------------------- Borselstra�e 16 f 22765 Hamburg T: +49408081803-29 F: +4940808180310 http://www.superReal.de Gesch�ftsf�hrer: Oliver Cloppenburg, Volker Will Amtsgericht Hamburg HRB 74092 Am 13.11.2012 um 16:56 schrieb Alexander Kludt: Hi there, thanks for joining the conversation, but as composer is just a compiled php application it can be run without command line access as well. Your point of legacy stuff is 100% correct - it will not work like that. I'm talking about the future here, means the next big release 6.0 or later, things will move on and so will developers. I just want to one central way of handling repos for modules, core, templates etc. (does not have to be composer) -- mit freundlichen Gr��en Alexander Kludt <logo.png> __________________________ Phone: 09283-5925453 Fax: 09283-592671 Skype: kingschnulli Email: cod...@aggrosoft.de Website: www.aggrosoft.de __________________________ Aggrosoft it intelligence GbR Tannstrasse 12 95111 Rehau GERMANY Sitz Rehau, Amtsgericht Hof Steuernummer: 223/165/54508 Ust.-Id. Nr. gem�� � 27 a Umsatzsteuergesetz: DE260722773 ___________________________ Diese Nachricht ist nur f�r den Empf�nger () bestimmt, sollten Sie nicht der Empf�nger sein l�schen Sie diese Nachricht umgehend und geben Sie uns bitte per Email (cod...@aggrosoft.de) Bescheid �ber den f�lschlichen Erhalt. Danny Althoff 13. November 2012 16:51 Hi Alexander,   I don�t think this would solve a lot of problems, because not everyone has access to php itself by console, just having ftp/mysql-frontend. Also a lot of things would make updates better, i remember a short mailing about update-mechanics for modules.   But i agree to make upgrades/updates having less work left for admins, one-click-updates would also be nice (even wordpress is giving such simple things). But if you are updating the shop you are lacking a lot of elements: third-party-modules, legacy-themes, customized files, etc. its hard to automize (especially without refactoring a lot of things).     Regards,   Danny Althoff _____________________________________ Danny Althoff Software Developer Die SHOPtimisten,- Robertstr. 2 51105 K�ln Germany fon +49 (0) 221 913999 � 17 fax +49 (0) 221 913999 � 98 dalth...@die-shoptimisten.de www.die-shoptimisten.de Die Shoptimisten UG (haftungsbeschr�nkt), Gesch�ftsf�hrer: J�rg Scholtz Sitz der Gesellschaft ist K�ln, eingetragen beim Amtsgericht K�ln, HRB 67004 Wichtiger Hinweis: Diese E-Mail (inklusive etwaiger Anh�nge) ist vertraulich und nur f�r den Adressaten bestimmt. Wenn Sie diese E-Mail irrt�mlich erhalten haben, machen wir Sie darauf aufmerksam, dass Ihnen eine Kenntnisnahme, eine Vervielf�ltigung oder Weitergabe nicht gestattet ist. Bitte informieren Sie uns umgehend, l�schen Sie die E-Mail und vernichten Sie etwaige Ausdrucke. Important Note: This e-mail (including any attachments) is confidential and intended only for the use of the address(es) named herein. If you have received this e-mail in error, you are hereby notified that any review, copying or distribution of it is strictly prohibited. Please inform us immediately and destroy the original e-mail and any printouts.  P Save a tree...please don't print this e-mail unless you really need to         Von: dev-general-boun...@lists.oxidforge.org [mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Alexander Kludt Gesendet: Dienstag, 13. November 2012 16:40 An: dev-general@lists.oxidforge.org Betreff: [oxid-dev-general] Using Composer   Hi guys, we are playing around with symfony2 currently, they use composer for dependency management (http://getcomposer.org). Composer makes it easy to manage dependencies through one single file in the shop base path and makes updating parts or the complete application a breeze. If the Oxid development team would provide a composer file the shop could be managed using composer - but this would take some effort. If the whole "Oxid Universe" would follow this paradigma a shop update would be as easy as modifing the composer file and running: php composer.phar update Or if one wanted to only upgrade the core something like php composer.phar update oxid/eshop Same goes for modules that support this way of updating. This would take out the "update hell" most of the developers are facing right now. I know this is just a rough idea, I just wanted to hear your opinion about using a package managment like this to keep updates and dependencies simple. -- best Alexander Kludt <image.png> __________________________ Phone: 09283-5925453 Fax: 09283-592671 Skype: kingschnulli Email: cod...@aggrosoft.de Website: www.aggrosoft.de __________________________ Aggrosoft it intelligence GbR Tannstrasse 12 95111 Rehau GERMANY Sitz Rehau, Amtsgericht Hof Steuernummer: 223/165/54508 Ust.-Id. Nr. gem�� � 27 a Umsatzsteuergesetz: DE260722773 ___________________________ Diese Nachricht ist nur f�r den Empf�nger () bestimmt, sollten Sie nicht der Empf�nger sein l�schen Sie diese Nachricht umgehend und geben Sie uns bitte per Email (cod...@aggrosoft.de) Bescheid �ber den f�lschlichen Erhalt. _______________________________________________ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general Alexander Kludt 13. November 2012 16:40 Hi guys, we are playing around with symfony2 currently, they use composer for dependency management (http://getcomposer.org). Composer makes it easy to manage dependencies through one single file in the shop base path and makes updating parts or the complete application a breeze. If the Oxid development team would provide a composer file the shop could be managed using composer - but this would take some effort. If the whole "Oxid Universe" would follow this paradigma a shop update would be as easy as modifing the composer file and running: php composer.phar update Or if one wanted to only upgrade the core something like php composer.phar update oxid/eshop Same goes for modules that support this way of updating. This would take out the "update hell" most of the developers are facing right now. I know this is just a rough idea, I just wanted to hear your opinion about using a package managment like this to keep updates and dependencies simple. _______________________________________________ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general _______________________________________________ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general

_______________________________________________
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general