Portable GIS information
I was contacted by someone who has downloaded portable GIS, very sensibly asking for information on the postgresql connection details. When I tried to respond to this person, their email address bounced back with a permanent failure, so I thought I’d better write something here so he doesn’t think I’m not replying!
Now, I was sure that I had included a readme file specific to the postgresql installation, but it looks like the pixies might have eaten it. Anyhow: the very secret local username and password for postgresql on the USB stick are: postgres and grespost. Please take the opportunity to create your own username and password if you are concerned about security. Don’t say I didn’t warn you…
The next version (in a couple of months) will have better documentation- I promise. The trouble is that as every developer knows, creating documentation is the longest part of any project. If I had waited until I had some decent documentation I wouldn’t have released it at all, and believe me I’m glad I did, the reponse has been fabulous. I won’t, however, be including documentation about how to use the programmes, as the majority of them already have pretty good user manuals online- I will include links to them though. You can hold me to that if you like!
Hi,
I just tried to logon using the username password above in phpPgAdmin and it failed? Is this the right place to use them?
Hi MJ,
Yes, that username and password should work in phppgadmin. I just tried- and it worked for me- what error message are you getting?
Thanks
Jo
Oh rather embarassing, after a reboot i had forgotten to restart the server, thanks for your help.
I have also put UDIG on the usb key which was a very simple exercise, zipped up my install (on my vmware machine), copied it to the usbgis/apps, midfieid the tray menu and it works without any changes!
Tee hee- I had wondered about that but wasn’t going to ask!
Thanks for the information about uDig- that’s cool to know. It’s a difficult decision to know whether to add it in to the package permanently because it increases the size of the download even further. Having said that, I’m wondering about splitting the project into two and having a desktop package and a web-based package. That would work…
All the best
Jo