Add new flexible parameters and new logic of using of nominatim-docker

[altair86]

When I made these changes, my goal was:

to make nominatim deployment and update secure.

To do this, I added:

• New parameter SKIP_IMPORT, which allows skipping imports when we have a "naive" container that is intended only for updating
• I also had to add PGDATABASE to the documentation and change a few lines in which the nominatim database participates in order to avoid erroneous database deletion on production systems
• Based on this, I added new work cases called "Using an external PostgreSQL database and configuring with updating the data container"

Thank you for your work

[what-the-diff]

• Added PGDATABASE variable to init.sh and start.sh
• Changed default value of PGDATABASE from nominatim to $PGDATABASE in init.sh
• Fixed typo in line 49 (init script) - !-z -> ! -z

[leonardehrenfried]

I'm wondering why we even drop the database in the first place. Seems quite destructive.

@philipkozeny do you have an idea?

[philipkozeny]

@leonardehrenfried because the OG maintainer started doing that in the initial version he released, never questioned if we should continue with that behaviour to be honest ...

nominatim-docker/2.5/Dockerfile

Line 50 in 10fc9e4

sudo -u postgres psql postgres -c "DROP DATABASE IF EXISTS nominatim" && \

[altair86]

That because I try to make it safely.
It's OK, if you could change name, I think