Project

General

Profile

Actions

Bug #11052

closed

Missing documentation about how to use an external postgres server (but no multi-server rudder install)

Added by François ARMAND over 7 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Documentation
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Small
Priority:
36
Name check:
Fix check:
Regression:

Description

We have a documentation that explain how to use only the [rudder-db / everything else] for multi-server install: https://www.rudder-project.org/doc-3.1/_use_a_database_on_a_separate_server.html

But most people just want to use an existing PostgreSQL server, and just that (i.e: that can't install anything on the DB server)

The general knowledge (aka "Nicolas Charles" :) seems to say that the following procedure is to follow:

#in /opt/rudder/etc/rudder-web.properies
rudder.server-roles.db=<ip or hostname or DB server>
rudder.jdbc.url=jdbc:postgresql://<ip or hostname or DB server>:5432/rudder

# update DB password in /opt/rudder/etc/rudder-passwords.conf

# run agent to propagate configs
rudder agent run

# restart webapp if the agent run didn't did it

# log on and start a policy generation

This process must be tested and documented in a new paragraphe.


Related issues 1 (0 open1 closed)

Has duplicate Rudder - User story #6411: Documentation doesn't explain how to configure Rudder in case of splitted arch, when the DB is on Amazon RDSRejectedActions
Actions

Also available in: Atom PDF