![]() ![]() This remote PostgreSQL can be a server you manage, or can be provided by a cloud service such as Amazon RDS. Tower with remote DB configuration: This installs the Tower server on a single machine and configures it to talk to a remote instance of PostgreSQL as its database. A Clustered Tower setup must be installed with an external database (2 options available):.Any node can receive HTTP requests and all nodes can execute jobs. In this mode, multiple Tower nodes are installed and active. Tower can be installed in a high availability cluster mode. ![]() There is no need to supply certificates for RabbitMQ.įor OpenShift-based deployments, refer to OpenShift Deployment and Configuration. If this is set to true, then a single-use, “pinned” CA and server certificates will be generated by the install script. Rabbitmq_use_ssl (true/false) - controls whether the RabbitMQ node-to-node communications will be encrypted. These certificates should have a CN (or wildcard, subject alternate name, and so forth) that matches the hostname the Tower nodes will use to connect to the database server. ![]() Postgres_ssl_cert and postgres_ssl_key - must be supplied when postgres_use_ssl is true. It has no effect on an external database. when the Tower install script is doing the deployment of the database server). This only has any effect with an internal/embedded database (i.e. Postgres_use_ssl (true/false) - controls whether the PostgreSQL server will be configured to require SSL. ![]() If they are absent, a self-signed (untrusted) certificate will be generated at install time. These must either both be provided or both be absent. Web_server_ssl_cert and web_server_ssl_key allow the user to provide a certificate and key to be installed in the web server for the Tower UI and API. You can also set it to verify-full to enforce SSL with full verification of certificate trust. It defaults to prefer, which means if the database server offers SSL, the client will use it. Pg_sslmode controls the SSL functions of the PostgreSQL client, i.e., how the Tower server connects to the database. Settings available for a traditional Tower install: The database server should be on the same network or in the same datacenter as the Tower server for performance reasons. Tower will not configure replication or failover for the database that it uses, although Tower should work with any replication that you have. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |