On Wed, Jul 6, 2016 at 3:45 PM, Tom McKay <thomasmc...@redhat.com> wrote:

> I too have a desire to do some work (hacking) on atomic registry. I
> managed to compile dockerregistry, update the image, update atomic registry
> conf to use my new image, and restart everything. I wondered, though, what
> a real dev would do? I'd like to debug w/ an IDE connected to the running
> container, ideally. (I'm using Rubymine for dev on katello/Satellite-6).
>
> ​Tom, for Atomic Registry I would point you to the contrib documentation
of the underlying projects. For the registry backend that means
OpenShift[1]. For the registry web UI that means Cockpit[2]. Both of these
have instructions for using vagrant as a development environment running
from source, not a built image.

That said, I have successfully used this script[3] to hack on the registry
console "in place" using a running container.

[1] https://github.com/openshift/origin/blob/master/CONTRIBUTING.adoc
[2] https://github.com/cockpit-project/cockpit/blob/master/HACKING.md
​[3] https://gist.github.com/aweiteka/886441fb01261c95d44f20c45ad5544a​



> Please include me in any how-to-dev threads and discussions. Thanks!
>
> On Wed, Jul 6, 2016 at 3:09 PM, Joseph Jeffers <monp...@gmail.com> wrote:
>
>> Hello!
>>
>>  I am Joseph Jeffers and I have been interested in working on and
>> contributing to Project Atomic, specifically I have been looking at the
>> 'atomic' program itself. I have never really done operating system or core
>> app development (one of the reasons I have been trying to get involved with
>> this project!).
>>
>> I already have the VM running and such, but I am having issues figuring
>> out how to set up the development workflow and how do you test changes that
>> you make to the code? Specifically, are the tests designed to be run on
>> another system or the atomic host itself, and what is the canonical
>> procedure for running them?
>>
>> Thanks for any pointers!
>>
>> Joe Jeffers
>>
>
>

Reply via email to