[Flow] Best practices for using Composer and Git Flow with Flow Applications

[Christian Loock]

Yeah, this is basically how we do it now. The only down side I see 
there, ist that you actually have multiple compsoer.json files in each 
branch. But when you naming is acurate, this doesnt seem to disturb 
anybody. It just clutters up everything a bit


Am 10.09.2014 um 16:40 schrieb Rémy DANIEL:
> Hi
>
> I just foud this : http://stackoverflow.com/a/16360107/1053453
> And the pointer to composer's cli documentation :
> https://getcomposer.org/doc/03-cli.md#composer
>
> I tried this solution on my last project, and it works very well.
>
> Cheers
>
> --
> Rémy
>
> 2014-08-14 10:08 GMT+02:00 Christian Loock <chl at vkf-renzel.de>:
>
>> In order to use something like this, I would have to be able to tell surf
>> to use a specific composer.json file.
>>
>> Btw: The Mail you sent did not contain anything for your [1] Reference.
>> Was this supposed to be some sort of link? If yes, I would like to see it,
>> since I'd like to read up on this.
>>
>>
>>
>> On 14.08.2014 09:59, Rémy DANIEL wrote:
>>
>>> Hi
>>>
>>> It seams that composer has a way to specify another config file than
>>> composer.json [1]
>>> That way you could put your composer.json in the Configuration folder.
>>> This works :
>>>
>>>     COMPOSER="./Configuration/Production/composer.json" composer diagnose
>>>
>>> BUT : sadly it seems that is not implemented in every composer's command
>>> :-(
>>>
>>>     COMPOSER="./Configuration/Production/composer.json" composer validate
>>>     > ./composer.json not found.
>>>
>>> Maybe we could do something at the composer level.
>>> Anyway, I am interested in some of your findings about this.
>>>
>>> Cheers!
>>>
>>>
>>>
>>> --
>>> Rémy
>>>
>>>
>>> 2014-08-12 11:13 GMT+02:00 Christian Loock <chl at vkf-renzel.de>:
>>>
>>>   Hello there,
>>>> I am currently trying to set-up a surf deployment for our application. I
>>>> want to be able to deploy to three environments, a testing, staging and
>>>> production environment. We use git flow for our versioning, and have
>>>> composer for our flow packages. As with the default flow installation, we
>>>> have a base distribution, that has it's own composer.json, that then
>>>> references our packages. Now, for every branch (eg. master, develop and
>>>> feature / release branches) I want to have an own composer.json file,
>>>> that
>>>> references to the corresponding branch of the packages.
>>>>
>>>> For example, in the composer.json of the develop branch for the base
>>>> distribution, I want all packages to be referenced by version
>>>> dev-develop.
>>>> You can just do this for every branch, but everytime you make an edit to
>>>> your composer.json and merge branches, it will mess up (eg. overwriting
>>>> version constraints etc.).
>>>>
>>>> I wonder if there are any best practices or tricks for those scenarios. A
>>>> nice case would be, if I could somehow have a seperate composer.json for
>>>> every branch, that is never automatically merged. I have done some
>>>> research
>>>> on this, but I was not able to find a good solution for this problem.
>>>>
>>>> I wonder, if anybody in this mailing list is running a comparable setup
>>>> and could share how they do it.
>>>>
>>>> Thank you very much.
>>>>
>>>> --
>>>> Christian Loock
>>>> Web Developer
>>>> Renzel Agentur
>>>> www.renzel-agentur.de
>>>>
>>>> _______________________________________________
>>>> Flow mailing list
>>>> Flow at lists.typo3.org
>>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
>>>>
>>>>   _______________________________________________
>>> Flow mailing list
>>> Flow at lists.typo3.org
>>> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
>>>
>> --
>> Christian Loock
>> Web Developer
>> Renzel Agentur
>> www.renzel-agentur.de
>>
>> _______________________________________________
>> Flow mailing list
>> Flow at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow
>>
> _______________________________________________
> Flow mailing list
> Flow at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow