From f95d5fa62e65ae2bdf0c6885ca5ac4d71d0512c0 Mon Sep 17 00:00:00 2001
From: infinite-persistence <inf.persistence@gmail.com>
Date: Thu, 14 Jul 2022 20:33:41 +0800
Subject: [PATCH] config: add commit ID

Primary impetus is to determine whether the reported TUS errors are due to old code, but the commit ID can be re-used in other areas where it makes sense.

The value comes externally from the command line, e.g.:
  `COMMIT_ID=$(git rev-parse HEAD) NODE_ENV=development yarn dev:web`
---
 config.js | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/config.js b/config.js
index 8cc4c0a65..fd5e21f51 100644
--- a/config.js
+++ b/config.js
@@ -93,6 +93,10 @@ const config = {
 
   AD_KEYWORD_BLOCKLIST: process.env.AD_KEYWORD_BLOCKLIST,
   AD_KEYWORD_BLOCKLIST_CHECK_DESCRIPTION: process.env.AD_KEYWORD_BLOCKLIST_CHECK_DESCRIPTION,
+
+  // FROM COMMAND LINE
+  COMMIT_ID: process.env.COMMIT_ID,
+  NODE_ENV: process.env.NODE_ENV,
 };
 
 config.SDK_API_PATH = `${config.LBRY_WEB_API}/api/v1`;