Hi, I tried checking out your fork too and got the same situation. It checks out onto the "je/42cc_7659" branch for some reason - not sure why. And that is a very old branch. If you switch to the master branch then the files are all there.
-Dave On 2/6/19 2:28 AM, Noumbissi Valere wrote: > The clone of my fork doesn't have the docker-compose.yml file eventhough am > able to see the file in my forked repo online. don't why when i do *git > clone*, i don't that file shipped down to my local repo. > > On Tue, Feb 5, 2019 at 7:40 PM Dave Brondsema <d...@brondsema.net> wrote: > >> Hi, >> >> There should be a "docker-compose.yml" file in your forked repo too. I >> would >> suggest just double checking that the clone of your forked repo is ok and >> that >> you are in the right directory - you should be in the top-level directory, >> not >> the "Allura" subdirectory. >> >> Otherwise, it also sounds similar to an issue that can happen if the >> top-level >> directory name isn't "allura" and your Docker version is less than 1.7.0. >> However, if you use this in your command prompt it should work still in >> that >> situation: export COMPOSE_PROJECT_NAME=allura >> >> On 2/5/19 11:42 AM, Noumbissi Valere wrote: >>> @Dave i was able to successfully installed it using docker. my mistake >> was >>> that i was using the clone of my forked instead of using the clone of the >>> master. But i expected the clone of my fork to work as well. could this >> be >>> a bug? >>> >>> On Tue, Feb 5, 2019 at 10:44 AM Noumbissi Valere < >> noumbissival...@gmail.com> >>> wrote: >>> >>>> This is the procedure i took before arriving here: >>>> i first forked the repo as directed by the contribution guide. >>>> next, i cloned my forked repo. >>>> But when i run the *docker-compose build* as directed in the >> installation >>>> guide, i get that error. >>>> When i look into the cloned directory, i can't find the >> docker-compose.yml >>>> and docker-compose.yaml >>>> >>>> On Tue, Feb 5, 2019 at 8:06 AM Noumbissi Valere < >> noumbissival...@gmail.com> >>>> wrote: >>>> >>>>> when i try to to do *docker-compose build*, it throws me the following >>>>> error >>>>> ERROR: >>>>> Can't find a suitable configuration file in this directory or >> any >>>>> parent. Are you in the right directory? >>>>> >>>>> Supported filenames: docker-compose.yml, docker-compose.yaml >>>>> >>>>> >>>>> On Mon, Feb 4, 2019 at 11:36 PM Dave Brondsema <d...@brondsema.net> >>>>> wrote: >>>>> >>>>>> Hi Noumbissi, >>>>>> >>>>>> Unfortunately attachments don't work on this mailing list, can you >> paste >>>>>> the >>>>>> error as text, or upload the image to imgur.com or something like >> that? >>>>>> >>>>>> As far as using Docker (which is easier than the step-by-step), that >>>>>> should work >>>>>> fine with a git clone. What error do you get with it? >>>>>> >>>>>> -Dave >>>>>> >>>>>> On 2/4/19 5:09 PM, Noumbissi Valere wrote: >>>>>>> I get the error below when i follow the step-by-step installation >> guide >>>>>>> described in the docs. please can someone direct me on how to solve >>>>>> this problem? >>>>>>> Thanks. >>>>>>> >>>>>>> On Mon, Feb 4, 2019 at 6:44 PM Dave Brondsema <d...@brondsema.net >>>>>>> <mailto:d...@brondsema.net>> wrote: >>>>>>> >>>>>>> On 2/4/19 8:57 AM, Noumbissi Valere wrote: >>>>>>> > Hello World, >>>>>>> > Am Noumbissi Valere Gille G. A 4th year Computer Engineering >>>>>> student from >>>>>>> > the University of Buea-Cameroon. am experienced in python and >>>>>> django and i >>>>>>> > will love to contribute to Allura and hopefully participate in >>>>>> gsoc 2019 >>>>>>> > with Allura. >>>>>>> > >>>>>>> > Thanks, regards >>>>>>> > >>>>>>> >>>>>>> Hi, welcome! >>>>>>> >>>>>>> I'd suggest taking a look at the Allura documentation at >>>>>>> https://forge-allura.apache.org/docs/ and get it up and running >>>>>> so you can begin >>>>>>> to familiarize yourself with it. It is a quite large codebase >>>>>> (although divided >>>>>>> into packages to help keep it well-organized). Let us know if >> you >>>>>> have any >>>>>>> questions as you get familiar with it. Small updates or fixes >>>>>> would be great >>>>>>> initial contributions. >>>>>>> >>>>>>> -Dave >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Dave Brondsema : d...@brondsema.net <mailto:d...@brondsema.net> >>>>>>> http://www.brondsema.net : personal >>>>>>> http://www.splike.com : programming >>>>>>> <>< >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Dave Brondsema : d...@brondsema.net >>>>>> http://www.brondsema.net : personal >>>>>> http://www.splike.com : programming >>>>>> <>< >>>>>> >>>>> >>> >> >> >> >> -- >> Dave Brondsema : d...@brondsema.net >> http://www.brondsema.net : personal >> http://www.splike.com : programming >> <>< >> > -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming <><