GPC does not require huge configuration steps. The only thinks you really need is a connection to a working PostgreSQL database server.
When you launch GPC for the first time, the application looks in the database for required tables ; if these required components can't be found, the application suggest you to create them ; you can validate if you have the required rights granted on the database.
The list of created components required by GPC are listed in the Database chapter.
The only think which MUST be defined is the GPC "repository" root dir. This directory can be used to store images relatively to the specified value, instead of using absolute paths.
When you have several users sharing an images directory over a network with different mount points, you can specify a different repository root dir for each user and then, each user will be able to visualize images stored in this repository without problem. This is used also when you want to have a correct access to your images directory from other tools, like the PHP3 GPC module, for with the repository base dir may be completely different.
![]() | Notice |
---|---|
Films and images can now be stored in absolute or relative modes. When a film is added into GPC database, his directory is stored in relative mode if it is in a subdirectory of the GPC repository, and it is stored in absolute mode in other cases. Films pathnames which are stored in relative mode just start with "./". |