[EnMasse] repository composition

[Vanessa Busch]

Hi Ulf,

  That is wonderful about the router-mage repo.  Configuration such as
run_qdr.sh, I would leave with the Dockerfile.  I have pulled out and
converted to yaml the projects for mqtt-lwt, mqtt-gatewy, topic-fowarder
etc as well.  The only issue with pushing them at this point, is that dogen
requires md5sums for the artifacts.  And this doesn't work for 'latest',
where it keeps changing.  But dogen will have this functionality very
shortly
https://github.com/jboss-dockerfiles/dogen/issues/105#issuecomment-294813510

Thank you,
Vanessa



On Tue, Apr 18, 2017 at 9:00 AM, Ulf Lilleengen <ulilleen at redhat.com> wrote:

> Hi Vanessa,
>
> I created https://github.com/EnMasseProject/router-image today exactly
> for this purpose. Also I have a branch https://github.com/EnMasseProj
> ect/dockerfiles/tree/move-artifact-creation that leaves only the Makefile
> and the Dockerfile.
>
> Right now, all configuration is part of the router-image repository, but
> I'm thinking perhaps they belong together with the Dockerfile? I think it
> would make sense to reuse those across different router builds.
>
>
>
> On 18. april 2017 14:57, Vanessa Busch wrote:
>
>> Hi Ulf,
>>
>>   I am continuing to convert the Dockerfiles to yaml for dogen.  As I do
>> this, I am moving them into the dockerfiles repo.
>>
>>   Would it be possible to have the product build for
>> dockerfiles/qdrouterd, moved onto its own repo?  And then what would be
>> left in dockerfiles/qdrouterd, would just be to pull the artifact?
>>
>> Thank you,
>> Vanessa
>>
>
> --
> Ulf
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/enmasse/attachments/20170418/e72af4d5/attachment.htm>