OpenEMR Development Demos

bradymiller wrote on Saturday, February 01, 2014:

Hi,
Just worked for me.
-brady
OpenEMR

bradymiller wrote on Saturday, February 01, 2014:

Hi,

The demo appliance starts off as a seed and is pluripotent. Once an ip address has been assigned to the demo appliance, it now has a genetic code to follow for growth:

A user whom wants to change what git repo/branch is served on the demo needs to know the ip address, so figured it made sense to title them by the ip address. I made this so you don’t need to be a developer to test code in any of the public git repositories. See here for instructions on how to do this:
http://www.open-emr.org/wiki/index.php/Development_Demo#UP_FOR_GRABS_Development_Demos
(as an exercise, try to point one of them to:
repo: https://github.com/yehster/openemr.git
branch: infant-sick
)

-brady
OpenEMR

bradymiller wrote on Saturday, February 01, 2014:

oops,
the link for instructions on setting up your chosen repo on an UP FOR GRABS demo is here:

blankev wrote on Saturday, February 01, 2014:

I leave it as is. Could have to do with me being a non-programmer… just a GP-User.

bradymiller wrote on Sunday, February 02, 2014:

Hi,

Realized today that this same demo farm mechanism could be leveraged to build the productions demos (ie. the ones that have sample data and users in addition to working offsite/onsite portals). Replaced the prior 4.1.1 demo and placed a demo for 4.1.2. Also updated the wiki.

If curious, can see how it works here:


(note the “pieces” directory stores the sample sql files for the 4.1.1 and 4.1.2 production demos and the “ssh” directory stores the stuff needed to connect to the offsite demo)

-brady
OpenEMR

blankev wrote on Sunday, February 02, 2014:

Tnx for this extra info. I included this information in the FAQ WIKI page, with reference to the Category Demo.

If you find some time, please check if I used the correct info for the correct Demo.

Tnx in advance.