Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

The HDX Demo Server is a copy of HDX that can be used to training and testing.  It is public and accessible to anyone. For purposes of this document, we will refer to the "real" HDX as the HDX Production Server.

Anything done on the HDX Demo Server will be deleted on Sunday morning (00:00 UTC) when the database is refreshed with the latest copy from the HDX Production Server.  There are two kinds of refresh of the HDX Demo Server

  1. Every week on Sunday at 00:00 UTC, the database is deleted and replaced with a fresh copy from the HDX Production Server. Downtime for the HDX Demo Server is usually less than one hour. This will copy all datasets, users, and organizations from the HDX Production Server to the HDX Demo Server and delete anything that was created on the Demo Server.
  2. The first Sunday of every month, in addition to the database refresh described above, the codebase of the HDX Demo Server is updated to match the latest version of the code on the HDX Production Server.  This brings in any new features, bug fixes, etc.  This update is more extensive and downtime is normally less than 5 hours.

Much of HDX's functionality requires a user account, and for the user to be part of an organization on HDX.  If you have one, you can use your user account and organization from the HDX Production server.  If you don't have one, there is a list of demo users, organizations, and locations available below.   

Rules of the Road

  1. Remember that the HDX Demo Server, although not indexed by most search engines, is still public on the internet.  Be thoughtful about content you create there. It's always best to clearly indicate that a user/dataset/organization you create is not "real". 
  2. Remember that you will lose your work every Sunday at 00:00 UTC.   If that presents a problem for your planned demo or training, please contact hdx@un.org and we can suspend the refresh. 
  3. If you are using the demo server extensively, it is recommended to let your planned use times be known in our Slack channel where any irregular updates/refreshes to the HDX Demo Server are announced.  Contact hdx@un.org to get added to the Slack channel. Use the following procedure to manage your reserved time:
    1. Post a message in the above mentioned Slack channel, mentioning the purpose of the reservation (e.g. X training) and estimated duration (e.g. 3 weeks).
    2. Use the reminder feature of Slack to set a remainder on the above mentioned channel like this: /remind #demo-feature-servers "X training" Apr 25 (where "Apr 25 is the estimated finish date)
    3. When the training is actually over, please post a reply on your initial post, checking the "Also sent to #demo-feature-servers" option, stating that the training is over and that the automatic refresh can be enabled once again.

Test Users, Organizations, and Locations available on the Demo Server

Location

Foolandia (FOO)

https://demo-data.humdata.org/group/foo

Organizations and their members

Demo Organization Alpha

Username

Email

Password

Role

user10

user10@test.com

pass10

admin

user11

user11@test.com

pass11

admin

user12

user12@test.com

pass12

editor

user13

user13@test.com

pass13

editor

user14

user14@test.com

pass14

editor

user15

user15@test.com

pass15

editor

user16

user16@test.com

pass16

editor

user17

user17@test.com

pass17

editor

user18

user18@test.com

pass18

editor

user19

user19@test.com

pass19

editor


Demo Organization Bravo

Username

Email

Password

Role

user20

user20@test.com

pass20

admin

user21

user21@test.com

pass21

admin

user22

user22@test.com

pass22

editor

user23

user23@test.com

pass23

editor

user24

user24@test.com

pass24

editor

user25

user25@test.com

pass25

editor

user26

user26@test.com

pass26

editor

user27

user27@test.com

pass27

editor

user28

user28@test.com

pass28

editor

user29

user29@test.com

pass29

editor


Demo Organization Charlie

Username

Email

Password

Role

user30

user30@test.com

pass30

admin

user31

user31@test.com

pass31

admin

user32

user32@test.com

pass32

editor

user33

user33@test.com

pass33

editor

user34

user34@test.com

pass34

editor

user35

user35@test.com

pass35

editor

user36

user36@test.com

pass36

editor

user37

user37@test.com

pass37

editor

user38

user38@test.com

pass38

editor

user39

user39@test.com

pass39

editor


Demo Organization Delta

Username

Email

Password

Role

user40

user40@test.com

pass40

admin

user41

user41@test.com

pass41

admin

user42

user42@test.com

pass42

editor

user43

user43@test.com

pass43

editor

user44

user44@test.com

pass44

editor

user45

user45@test.com

pass45

editor

user46

user46@test.com

pass46

editor

user47

user47@test.com

pass47

editor

user48

user48@test.com

pass48

editor

user49

user49@test.com

pass49

editor


Demo Organization Echo

Username

Email

Password

Role

user50

user50@test.com

pass50

admin

user51

user51@test.com

pass51

admin

user52

user52@test.com

pass52

editor

user53

user53@test.com

pass53

editor

user54

user54@test.com

pass54

editor

user55

user55@test.com

pass55

editor

user56

user56@test.com

pass56

editor

user57

user57@test.com

pass57

editor

user58

user58@test.com

pass58

editor

user59

user59@test.com

pass59

editor


Demo Organization Foxtrot

Username

Email

Password

Role

user60

user60@test.com

pass60

admin

user61

user61@test.com

pass61

admin

user62

user62@test.com

pass62

editor

user63

user63@test.com

pass63

editor

user64

user64@test.com

pass64

editor

user66

user66@test.com

pass66

editor

user66

user66@test.com

pass66

editor

user67

user67@test.com

pass67

editor

user68

user68@test.com

pass68

editor

user69

user69@test.com

pass69

editor


  • No labels