Purpose

If you're running Synchrony standalone in a cluster, and you prefer to store sensitive information in your environment, rather than directly in the Synchrony startup scripts you can create a synchronyenv file, and use it to provide your database credentials. 

These instructions are for Linux users. We'll assume your dedicated Synchrony user is named synchrony.

Steps

Create the synchronyenv file

1. Change to your Synchrony user, for example:

   sudo su - synchrony

2. In your <synchrony-home> directory, create a new file called synchronyenv.

3. Add the following lines to the synchronyenv file, and include your database credentials.

   export SYNCHRONY_DATABASE_USERNAME="database-username"
   export SYNCHRONY_DATABASE_PASSWORD="database-password"

4. Make sure to make this file executable, so it can be sourced by start-synchrony.sh

   chmod +x synchronyenv

Modify your Synchrony startup script

1. Edit your start-synchrony.sh  script. 

2. Comment out the following lines

   DATABASE_USER="<DB_USERNAME>"
   DATABASE_PASSWORD="<DB_PASSWORD>"

   Note that they may already be commented out, or have slightly different information. 
   
   

3. Uncomment the following line, and include the path to the synchronyenv file you've just created.

   SYNCHRONY_ENV_FILE="<PATH_TO_ENV_FILE>"

4. Save your changes. 

Modify your shell profile

Bash as login shell will load the following profiles in order. Your environment may vary, but this is an example for Ubuntu:

• /etc/profile
• ~/.bash_profile
• ~/.bash_login
• ~/.profile

Note: Bash as non-login interactive shell will load ~/.bashrc

1. Edit the appropriate profile as noted above, and to add the following code:

   # Defines the absolute path to the synchronyenv file. 
   # For example, if your synchronyenv file was located in
   /opt/synchrony-home/synchrony, you would use the example:
   source /opt/synchrony-home/synchrony/synchronyenv

2. Confirm the variables are in place by exiting the bash session of the Synchrony user, then re-entering it, and running the following command:

   env

3. Your database credentials defined should appear in your env output. Here's a sanitized example:

   XDG_SESSION_ID=15
   SYNCHRONY_DATABASE_PASSWORD=<sanitized>
   ...
   SYNCHRONY_DATABASE_USERNAME=<sanitized>
   ...
   _=/usr/bin/env