dhis2-devs team mailing list archive

[Lars Helge Øverland <lars@xxxxxxxxx>]

Hi Sultan,

I don't have experience with exactly this scenario. How do you distribute
your machines to the field? A simple approach would be to simply:

- create a metadata JSON file containing everything you need to reflect the
current state of the metadata
- create a small executable that uses curl to -x POST -d @file this to the
metadata API endpoint
- package this executable and the JSON file on the file system and have
your user invoke it after starting up for the first time


regards,

Lars







On Mon, Jun 6, 2016 at 6:34 AM, Sultanahamar Mohammad <
sultanm@xxxxxxxxxxxxxxxx> wrote:

> Hi All,
>
> This mail is to understand the practices that you follow while
> provisioning a new dhis instance with metadata in central and field dhis
> model.
>
>                     Our setup is something like this. We have a central
> instance of dhis in cloud and we have multiple instances of dhis in
> different locations. Metadata would be created at central instance, flows
> down to the field instances and data would flow upward.
>
>                      We are thinking on how can we easily setup a dhis
> machine with metadata in a field which starts quite late may be 2 years
> after the cloud instance is setup and there might be lot of metadata
> already in place. If you have done something like this already, please let
> us know on how do you handle this.
>
> Thanks  in advance.
>
> Regards,
> Sultan Ahamar.
> Thought Works.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Lars Helge Øverland
Lead developer, DHIS 2
University of Oslo
Skype: larshelgeoverland
lars@xxxxxxxxx
http://www.dhis2.org <https://www.dhis2.org/>