Problems in setup the project

[Mário Areias]

Hello everyone,

I started to setup my environment, so I forked the buendia repo and started to follow this doc about how to setup OpenMRS. It was everything going fine until I ran the the script tools/openmrs_setup dev and then I got this error:

Submodule 'db-snapshot' (g...@github.com:mario-areias/db-snapshot) registered for path 'db-snapshot'
Cloning into 'db-snapshot'...
ERROR: Repository not found.

So there is a git submodule configured on buendia repository, but it was looking for this submodule in my github account rather than in buendia account. When I checked the .gitmodules file I found this:

[submodule "client"]
        path = client
        url = ../client
[submodule "db-snapshot"]
        path = db-snapshot
        url = ../db-snapshot

The url for these submodules are relative and that's why git was trying to find the submodule in my account. So there a few options to fix this:

1) Change the URLs to use absolute path like: g...@github.com:projectbuendia/db-snapshot.git

2) Everyone who is gonna be a volunteer, will be added to the Project Buendia organisation in github (and there is no need to fork any repo)

3) Every volunteer working on the backend should fork all three repositories (buendia, db-snapshopt, clients)

I don't know how these repositories interact with each other, but I believe solution 1 is the best one. It is simple and easy to do it. Solution 3 is quite annoying and solution 2 is not ideal, specially with so many new contributors joining.

I will make the solution 1 fix in my local to complete the setup. If people are happy with that fix I can make a PR to fix in the buendia repo as well. If there is a better solution than that, please let me know.

Cheers,

Mário

[Dan Cunningham]

At first glance Solution 1 sounds best to me also, though what would you do if you wanted instead to use your own locally cloned version of db-snapshot?

--
Project Buendia
http://www.projectbuendia.org
Source code and docs at https://github.com/projectbuendia/buendia/wiki
Twitter @ProjectBuendia
---
You received this message because you are subscribed to the Google Groups "Buendia developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to buendia-dev...@googlegroups.com.
To post to this group, send email to buend...@googlegroups.com.
Visit this group at http://groups.google.com/group/buendia-dev.
To view this discussion on the web visit https://groups.google.com/d/msgid/buendia-dev/CACp98asr_5G1FsmEo7WH6JnXm8aRyUJXT5f85JWNhkWky%3DdVzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Dan Cunningham

d...@possibility.design

+447964404897

Skype: djcunning

@dancunningham

linkedin.com/in/dancunningham

[Mário Areias]

That's a good point. As I said, I don't know how these modules interact with. However, looking at contributors of db-snapshot, it seems the person who has most contributed by far is Jenkins :)

In short term, we can use solution 3 and make everyone fork all required repositories and keep them updated and so on. In long term, we might want to move away from submodules and use them as maven dependency instead. It would be better to manage and easier to update.

[Dan Cunningham]

Ah yes, Jenkins is automatically making a snapshot of the database at dev.projectbuendia.org

In view of that, I guess solution 1 makes most sense.

+Ping Y do you agree?