Share

PostgreSQL Database



When installing the application or the Project server, PostgreSQL (a Database Management System or DBMS) is installed. Flame Family products then use a database served by PostgreSQL to manage some project-related metadata, replacing the legacy Stone+Wire database. A single database is required to store the information for all the projects you will create in your facility.

In a workgroup environment, administrators might prefer to use a Project server instead of a local database since there is no obligation to create a local database. It is also possible to work in a mixed local and remote database environment like in previous versions of Flame Family products.

This new infrastructure brings the following changes and improvements:

  • No more 8-volume limit as with Stone+Wire
  • Project-based Cache and Renders, enabling easier data management
  • Automatic configuration for small studios and freelancers who do not need an extra level of security
  • Improved security using users and groups access for secured projects, as well as encrypted network communication
  • The new command-line tool igniter to ease the deployment and management of Flame Family products databases
Note: Only a single database can exist on a given host; all projects on that host will share the same database.


The flame_db user

Installing a Flame Family product creates a flame_db user on your workstation. This user is the only one who can manage the various database operations like:

  • Creating a Certificate Authority
  • Creating and deleting a database
  • Adding and removing user access to the database, including certificates management
  • Adding and removing groups to the database

For standalone configurations, you do not need to interact with the flame_db user since the application will ask to elevate your privileges when a secured access is required. For more information, see Database Creation.

For more information on workgroup environments with remote hosts and project servers, see Database Creation and Project Server Configuration.



Database and Security

Flame Family products provide two levels of security for the database: trust and certificate authentication modes.

Warning: It is not possible to modify the security level of a database after it has been created. You must decide the security level required for your configuration prior to creating the database.

Trust Authentication Mode

The trust authentication mode allows any Flame Family product user to connect to and access the database. This is the default database access mode and matches the default security level of legacy Flame Family product versions.

Multiple users can work in a workgroup with this mode. For studios with an identity management solution, it is also possible to reduce access to projects and content using os-level user and group permissions, similar to legacy versions of the application. When starting the application for the first time on a workstation without a database, trust mode is used.

Visit Database Creation to learn how to create and manage a database in this mode.

Certificate Authentication Mode

The certificate authentication mode allows studios to manage access to projects and content created with the application with a more robust access management. It is based on a centralised Certificate Authority and relies on SSL user certificates to provide secure database access, authentication and encrypted communication.

In this mode, the database must be created with the igniter command-line tool and it is required to use an identity management solution. Network-accessible user home directories are strongly recommended.

Visit Database Creation to learn how to configure and manage a database in this authentication mode.

Was this information helpful?