docker: Set db_name and password through .env

.env.sample

@@ -0,0 +1,2 @@
+PINGER_DB_PASSWORD=passwrd
+PINGER_DB_NAME=pinger

.gitignore

@@ -4,3 +4,4 @@
 
 # Default config files
 /agent.yml
+/.env

deploy/pinger.apache.conf

@@ -1,7 +1,7 @@
 Listen 80
 <VirtualHost *:80>
-    ServerName pinger.staging.sdslabs.*
-    ServerAlias pinger.sdslabs.*
+    ServerName pinger.sdslabs.*
+    ServerAlias pinger.staging.sdslabs.*
     # Other directives here
     <Location />
         ProxyPass http://127.0.0.1:9010

docker-compose.yml

@@ -6,8 +6,8 @@ services:
     image: timescale/timescaledb:2.0.0-pg12
     # Setting environment variables for Timescale
     environment:
-      POSTGRES_PASSWORD: "password"
-      POSTGRES_DB: "pinger"
+      POSTGRES_PASSWORD: "${PINGER_DB_PASSWORD:-password}"
+      POSTGRES_DB: "${PINGER_DB_NAME:-pinger}"
     # Healthcheck conditions are defined since pinger service needs to know if Timescale has started
     # pg_isready is a binary that is available with the postgres image(timescale is built upon postgres)
     healthcheck:
@@ -24,6 +24,9 @@ services:
       timescale:
         condition: service_healthy
     build: ./
+    environment:
+      METRICS.DB_NAME: "${PINGER_DB_NAME:-pinger}"
+      METRICS.PASSWORD: "${PINGER_DB_PASSWORD:-password}"
     # PINGER_PORT is the port on the host machine where the service will be available. Set it through .env
     ports:
       - "${PINGER_PORT:-9010}:9010"

docs/src/contributing/build-process.md

@@ -67,6 +67,10 @@ $ make docker TAG="pinger:v1.2.3"
 A `docker-compose.yml` is also provided to get pinger started more easier.
 Just add an `agent.yml` according to your use case and then run `docker-compose up`.
 This will get both the timescale db and pinger container up and running in no time!
+For setting custom values for the Timescale DB's name and password, just run `cp .env.sample .env`
+and then change the values in the `.env` according to your need. The changes will reflect in both
+Timescale's and Pinger's container (overriding the name and password value set in `agent.yml`) without
+requiring you to make changes in multiple places.
 
 ## Documentation