Backend GKE Deploy, access key for backend
- Configs and automation for deploying backend to GKE - First steps to adding an optional token check for requests to backend - First steps frontend sending optional token to backend when configured
This commit is contained in:
parent
0fedaef537
commit
e6c2042df6
17 changed files with 296 additions and 39 deletions
20
sample.env
Normal file
20
sample.env
Normal file
|
@ -0,0 +1,20 @@
|
|||
# Copy this file over to .env and fill in the desired config.
|
||||
# .env will become available to docker compose and these values will be
|
||||
# used when running docker compose up
|
||||
|
||||
# Edit to set OpenAI access key
|
||||
OPENAI=ADD OPENAI KEY HERE
|
||||
|
||||
# Uncomment and edit to set GROQ access key
|
||||
# GROQ: ${GROQ}
|
||||
|
||||
# Uncomment and edit to set OLLAMA Url
|
||||
# OLLAMA_API_URL: ${OLLAMA_API_URL}
|
||||
|
||||
# Address and port of the remotely deployed Perplexica backend
|
||||
REMOTE_BACKEND_ADDRESS=111.111.111.111:0000
|
||||
|
||||
# Uncomment and edit to configure backend to reject requests without token
|
||||
# leave commented to have open access to all endpoints
|
||||
# Secret key to "secure" backend
|
||||
# SUPER_SECRET_KEY=THISISASUPERSECRETKEYSERIOUSLY
|
Loading…
Add table
Add a link
Reference in a new issue