add configurable postgres UID/GID

[bgruening]

This patch was provided by @chambm to fix the UID and GID of postgres. As far as I understood this will help in running this container with a Windows directory mounted into a VM that runs this container.

@chambm please provide more information as necessary.

I would appreciate any review and thoughts about this, especially if there are any concerns about backward compatibility.

@dpryan79, @kellrott, @jmchilton

[chambm]

It probably also affects OS X: #68 - most of the issues I saw when googling this were involving boot2docker and OS X, not Windows.

[bgruening]

And I don't have any of these to test ;)

[dpryan79]

The only obvious issue is that the current postgres id/gid are 102/106, so anyone doing a docker pull could run into problems.

[bgruening]

@dpryan79 I hope #73 will address this, what do you think?

[dpryan79]

Yeah, it looks like #73 will take care of this.

[bgruening]

@jmchilton I forgot that we wanted to migrate the startup script to the ansible playrole: galaxyproject/ansible-galaxy-extras#12
Do we want to do this now or in the next release?

[jmchilton]

@bgruening No need to prevent or slow your release based on that - I would like to do that some point but I don't have time this cycle. I'll make a note to update the ansible role to reflect this change though.

[bgruening]

@jmchilton ok, maybe I will find some time.
Are you ok with this PR?

[jmchilton]

@bgruening Absolutely - this looks great!

[bgruening]

@matted thanks for your contribution. In one hour there will be a new bgruening/galaxy-stable:dev image. Please test it if you have some time.
@dpryan79 if you also could test it before the next release this would be awesome!

[dpryan79]

@bgruening: Sure, when's the next release? I won't have time to test this today, but if I haven't gotten back to you by the time you come by on the 10th then remind me then.

[bgruening]

No clue when the next release will be. But 5 days we have at least.