Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • web server
  • geo server
  • localhost
    Each environment (DEV, QA, PROD) will have it's own web server and geoserver.
    See this diagram if it's not clear.
    We use postgres's hba.conf to control this access.
    Get the IPs for the hba.conf from Henry or Paul.
    We want to be as strict as is reasonable - not as strict as possible.

Users
I think know we'll want 3 at least 2 users:

  • postgres
  • eas_user
  • etl_user
  • geoserver

Let's discuss if there is any value in having additional users such as:

  • geoserver user
  • etl_user

Postgres User
The postgres user will be

...

  • needs to be able to read and write to all tables in the public schema in the mad databasemad and sfmaps databases
  • should we use a group or role here?

...

Geoserver User
The geoserver user user needs to be able to read all of the tables and views in the sfmaps DB.

...

...

  • to make things simple, we'll use eas_user for access from geoserver

For any new users, we'll need to set the correct access privileges.
Until now, I have been using the postgres user everywhere (sorry!).

Installation Errors

error:

Code Block
  configure: error: no acceptable C compiler found in $PATH

...