From 9c718cbc5f1c365f3ca36e9c106d3bc9f187e3f3 Mon Sep 17 00:00:00 2001 From: Dmitry Verkhoturov Date: Thu, 6 Jul 2023 12:14:30 +0300 Subject: [PATCH] clarify SharedSecret usage by comment It's not used aside from `server` but it was decided to keep it in place for backwards compatibility in PR #1544. --- backend/app/main.go | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/backend/app/main.go b/backend/app/main.go index 4118e238..ecdb3dbe 100644 --- a/backend/app/main.go +++ b/backend/app/main.go @@ -23,7 +23,8 @@ type Opts struct { CleanupCmd cmd.CleanupCommand `command:"cleanup"` RemapCmd cmd.RemapCommand `command:"remap"` - RemarkURL string `long:"url" env:"REMARK_URL" required:"true" description:"url to remark"` + RemarkURL string `long:"url" env:"REMARK_URL" required:"true" description:"url to remark"` + // SharedSecret is only used in server command, but defined for all commands for historical reasons SharedSecret string `long:"secret" env:"SECRET" required:"true" description:"the shared secret key used to sign JWT, should be a random, long, hard-to-guess string"` Dbg bool `long:"dbg" env:"DEBUG" description:"debug mode"`