Of your database is, and your external GitLab hostname For example, suppose the external hostname Note that server.crt and server.key may be different from the default SSLĬertificates used to access GitLab.
Gitlab-psql can access the directory in the files are placed in.įor more details, see the PostgreSQL documentation. The files for you, but if the paths are customized, you must ensure that the Must be readable by the gitlab-psql user. Note that the location of these files can be configurable, but the private key Prefer to use a CA-signed certificate or replace this with your own self-signed certificate, use the following steps. This isn’t required forĪ 10-year self-signed certificate and private key will be generated by Omnibus GitLab for use. opt/gitlab/embedded/ssl/certs/cacert.pem. A root certificate bundle that validates the server’s certificate ( root.crt).īy default, Omnibus GitLab uses the embedded certificate bundle in.The corresponding private key for the SSL certificate ( server.key).The public SSL certificate for the database ( server.crt).SSL support depends on the following files: Using the hostssl configuration in pg_hba.conf. Omnibus automatically enables SSL on the PostgreSQL server, but it will acceptīoth encrypted and unencrypted connections by default. To avoid errors like the one related to loading necessary libraries. It is highly recommended to restart PostgreSQL when the underlying version changes, Start aĭatabase console with sudo gitlab-psql, then replace in the following query Run a query against your database to determine if any individual setting requires a restart. Identifies which PostgreSQL settings require a restart and which require only a reload. PostgreSQL setting that requires a restart, you will need to restart PostgreSQL manually after you To do a reload of PostgreSQL on reconfigure, and not a restart. Because administratorsįrequently want more control over exactly when PostgreSQL is restarted, Omnibus has been configured With a reload (HUP), while others require PostgreSQL to be restarted. PostgreSQL is unique in that some of its settings will take effect Omnibus normally restarts any service on reconfigure if config settings for that service wereĬhanged in the gitlab.rb file. Using the PostgreSQL Database Service shipped with Omnibus GitLab Reconfigure and PostgreSQL restarts Use the packaged PostgreSQL server included with Omnibus GitLab (no.Thus you have two options for database servers to use with Omnibus GitLab: GitLab supports only the PostgreSQL database management system. Connecting to the PostgreSQL database Database settings.
#Update postgresql example how to#
UNIX socket configuration for non-packaged PostgreSQL.Using a non-packaged PostgreSQL database management server.Configuring multiple database connections.Revert packaged PostgreSQL server to the previous version.Opt out of automatic PostgreSQL upgrades.Store PostgreSQL data in a different directory.Enabling PostgreSQL WAL (Write Ahead Log) Archiving.Configure packaged PostgreSQL server to listen on TCP/IP.Automatic restart when the PostgreSQL version changes.Using the PostgreSQL Database Service shipped with Omnibus GitLab.
0 kommentar(er)
