Re: [Gnumed-devel] using cryptmount for postgresql cluster instance

[Karsten Hilbert]

Jim,

setting up the encryption involves three steps:


1) at the OS level define an encrypted location

This is being done with cryptmount. There are other ways but
this is what Syan tested. This can stay in EncryptingDevices.


2) at the database level tell PG to use that location

How to do that is described here for PG 7.4:

 http://www.postgresql.org/docs/7.4/static/manage-ag-alternate-locs.html

This works a little bit different for 8.0+ (it uses
tablespaces which is *slightly* different). We only support
the 7.4-way for now.

Instructions/links on this could on the page
ConfigurePostgreSQL within the first section. Maybe the
first two steps outlined here could be mentioned there ?


3) tell the bootstrapper to use that location for the new database

How this works is described here:

> >The bootstrapper now supports alternate locations for databases....
> >Just define alternate location =
> >...PGDATA2_GNUMED_V3 must be known to the PostgreSQL server as
> >an environment variable. ...

It is also documented in

 gnumed/server/bootstrap/bootstrap-standard.conf.template

For this, I suppose, a one-liner (like the above) in the
section on ConfigurePostgreSQL should suffice.


Thanks !

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346