Clarify experimental variables should not be changed for prod

[surchs]

We have had questions come up about this section:

recipes/template.env

Lines 78 to 86 in ef1dcc5

	# ---- SECURITY CONFIGURATION ----
	# NOTE: EXPERIMENTAL, THESE SETTINGS ARE UNDER ACTIVE DEVELOPMENT AND CURRENTLY SHOULD BE MODIFIED FOR DEV DEPLOYMENTS ONLY.
	# The below settings will be used for both the query tool and the f-API.
	# NB_ENABLE_AUTH=false
	# If NB_ENABLE_AUTH is set to true, you MUST provide a valid OAuth client ID for your query tool instance.
	# To obtain an OAuth client ID to enable login with Google, see https://developers.google.com/identity/openid-connect/openid-connect#appsetup.
	# NB_QUERY_CLIENT_ID=XXXX
	# --------------------------------

Specifically, folks were wondering how to make "Auth" work in the tool. In other words: the warning in the .env file above these settings is not a strong enough signal for folks to not try anyway to enable auth in production. That's not good. We should quickly find a better way to handle these variables.

We should remove the reference to Google Auth since we are no longer using that.

Either:

• make it unambiguously clear, that these variables are not to be changed in prod
• rename the variables to more clearly demonstrate that they are experimental and only for AuthN, not AuthZ
• remove these variables entirely from the template.env to avoid people ignoring the warnings
• introduce a "development context" variable somewhere that, if set to "production", either yells about these values or just strips them directly

[neurobagel-bot]

🚀 Issue was released in v0.5.0 🚀