Mercurial > gemma
view schema/demo-data/README @ 1501:048d1891e004
Fixed problem with accepting sounding result imports and moving them out of the staging area.
author | Sascha L. Teichmann <sascha.teichmann@intevation.de> |
---|---|
date | Wed, 05 Dec 2018 11:00:53 +0100 |
parents | 0c0826063561 |
children | 5e38667f740c |
line wrap: on
line source
------------------------------------------------------------------------ !!!!!! WARNING !!!!!! Data within this directory is provided for the sole purpose of testing and demonstration of the Gemma software. It is neither intended nor suitable for any kind of production use. THIS DATA CONTAINS UNSAFE AND PUBLICLY KNOWN PASSWORDS. DO NOT INSTALL ON REMOTE ACCESSIBLE SYSTEMS! ------------------------------------------------------------------------ Defined Users: | Username | Password | Role | Country | |----------+----------+------------------------+---------| | sophie | so2Phie4 | System Administrator | AT | | lucian | lu2Cian4 | Waterway Administrator | RO | | oana | oa2Na2 | Waterway User | RO | | penka | pe2Nka3 | Waterway Administrator | BG | | vanja | va2Nja3 | Waterway User | BG | Installation: We assume, you already have a database "gemma" with the Gemma schema in place. As postgres super user ("postgres" on most default installations): psql -f roles.sql -d gemma psql -f users.sql -d gemma psql -f responsibility_areas.sql -d gemma Acknowledgements: The file `responsibility_areas.sql' contains information made with Natural Earth. Free vector and raster map data @ naturalearthdata.com.