matty/pleroma-ollama-bot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

removed WS protocol token, since WS connections are unreliable

Browse Source
This commit is contained in:
matty
2025-07-05 00:12:52 +00:00
parent b4b656f808
commit ca4643092f
1 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
.env.example
View File

@ -5,5 +5,4 @@ ONLY_LOCAL_REPLIES="true" # reply to only users locally on your instance
OLLAMA_URL="http://localhost:11434" # OLLAMA connection URL OLLAMA_URL="http://localhost:11434" # OLLAMA connection URL
OLLAMA_SYSTEM_PROMPT="" # system prompt - used to help tune the responses from the AI OLLAMA_SYSTEM_PROMPT="" # system prompt - used to help tune the responses from the AI
OLLAMA_MODEL="" # Ollama model for responses e.g dolphin-mistral:latest OLLAMA_MODEL="" # Ollama model for responses e.g dolphin-mistral:latest
INSTANCE_BEARER_TOKEN="" # instance auth/bearer token (check the "verify_credentials" endpoint request headers in Chrome DevTools if on Soapbox) INSTANCE_BEARER_TOKEN="" # instance auth/bearer token (check the "verify_credentials" endpoint request headers in Chrome DevTools if on Soapbox)
SOAPBOX_WS_PROTOCOL="" # this is the header required to authenticate to the websocket. No idea why Soapbox does it like this. You can get it in the request headers for the socket in Chrome DevTools