Docker update (looking for testers)

[Long Vu]

On Wed, Nov 15, 2017 at 12:04 PM, Dominik Ruf <dominikruf at gmail.com> wrote:
>
>
> Long Vu <long.vu at intelerad.com> schrieb am Di., 14. Nov. 2017 um 23:33 Uhr:
>>
>> On Tue, Nov 14, 2017 at 4:55 PM, Dominik Ruf <dominikruf at gmail.com> wrote:
>> >
>> >
>> >
>> > Thomas De Schampheleire <patrickdepinguin at gmail.com> schrieb am Di., 14.
>> > Nov. 2017 um 21:32 Uhr:
>> >>
>> >> Hi Dominik,
>> >>
>> >> 2017-09-20 20:52 GMT+02:00 Dominik Ruf <dominikruf at gmail.com>:
>> >> > Hi all,
>> >> >
>> >> > like I mentioned before, I'd like to add a Dockerfile and
>> >> > docker-compose.yml
>> >> > to make it really easy to get started with kallithea.
>> >> > I did some more work on my docker setup and it now also includes ssh
>> >> > support.
>> >> > And like before it generates the css file from less.
>> >> > So since these 2 things are not merged yet, I'd like to wait before
>> >> > creating
>> >> > a PR.
>> >> >
>> >> > But I wanted to ask if some people would volunteer to already test
>> >> > it.
>> >> > I'd like to hear from others if it helps them setting up a Full Stack
>> >> > installation.
>> >> > And if there are unclear things about how to use it.
>> >> >
>> >> > I upload my images to
>> >> > https://hub.docker.com/r/domruf/kallithea-domruf/
>> >> > and you can find the docker-compose.yml at
>> >> >
>> >> > https://kallithea.dominikruf.com/kallithea/kallithea-domruf/raw/26ccf792b435/docker/docker-compose.yml
>> >> >
>> >>
>> >> Sorry, I kind of forgot about this mail.
>> >>
>> >> I have recently deployed a kallithea instance with docker based on
>> >> your repo, but I was unaware that the version on Bitbucket is not up
>> >> to date with your latest developments.
>> >> As a result, I was still working on top of the latest commit there:
>> >>
>> >> https://bitbucket.org/domruf/kallithea-docker/commits/36265eeea7a94a3538dbdb2e9cf22f0f56252965
>> >> I would need to reevaluate your changes on dominikruf.com. For the
>> >> text below, I have not yet done that. It is possible that you already
>> >> solved some problems.
>> >
>> > I did some experiments and some back and forth, so the history of my
>> > repo is a bit ugly. Sorry.
>>
>> Since that is your own host and you are the author of the "repository
>> settings (phases) v5 PR"
>> (https://bitbucket.org/conservancy/kallithea/pull-requests/343), why
>> don't you enable evolve on your own instance yourself to use named
>> branch instead of anonymous branch and to avoid multiple "similar"
>> heads.  That would clean up quite some mess. ;D
>
> I do use evolve on my own instance.
> How do you think named branches would help?

The way I leverage evolve at work is each personal branch is a named
branch so we know all revs on that same branch very easily.

For release, to strip the personal branch name out, we rebase on
default and the personal branch name disappear.

Collaborating on the same branch is easier to, but do not apply since
you are alone on your branch.

Since you use evolve, why don't you prune all the heads on default
that do not have a bookmark?  I assume all the heads with bookmarks
are the active ones and the rest are not.  Sorry if wrong assumption.

Each tag on the Docker hub is one "feature/bookmark" you are working
on?  And they are being rebase often on top of tip of default of the
kallithea repo on bitbucket?  If you do, thanks for taking the time to
keep them up-to-date.


-- 
Long Vu | Build Controller | Intelerad | +1-514-931-6222 ext. 7743

-- 

This email or any attachments may contain confidential or legally 
privileged information intended for the sole use of the addressees. Any 
use, redistribution, disclosure, or reproduction of this information, 
except as intended, is prohibited. If you received this email in error, 
please notify the sender and remove all copies of the message, including 
any attachments.