Add config options, default configuration and support for Azure OpenAI#32
Add config options, default configuration and support for Azure OpenAI#32itbm wants to merge 1 commit into
Conversation
|
I currently have my chatbot accessible through Cloudflare tunnels with authentication. On a network that blocks *.openai.com, when I enter my API key, it gets blocked when validating. I assume adding it to the config file would bypass the initial check... at that point, does the server hosting Chatbot handle all communications with openai.com or is the client browser still making calls to openai? |
|
If you are blocking the API endpoint, I would advise you to unblock it to
ensure a proper connection. Any issues that arise from blocking the
endpoint are yours to solve.
…On Wed, Apr 5, 2023 at 10:07 PM wescrockett ***@***.***> wrote:
I currently have my chatbot accessible through Cloudflare tunnels with
authentication. On a network that blocks *.openai.com, when I enter my
API key, it gets blocked when validating. I assume adding it to the config
file would bypass the initial check... at that point, does the server
hosting Chatbot handle all communications with openai.com or is the
client browser still making calls to openai?
—
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APESZJS4TK6FDEHNBHIKOUDW7XUKHANCNFSM6AAAAAAWMGK6Z4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
Ah, yeah, i understand that for sure. Let me rephrase though (meant it as a general question): Other than validating the API key, does the server running the interface act as a proxy for the API or are the API calls still made client side? I am running the interface on a home server and accessing the server from a network that has openai.com blocked. My hope was that all requests/responses to/from api.openai.com would be handled server side. If that isn't how this is made, that's fine, just trying to make sure I understand it. Thank you. |
|
@wescrockett This is a client-side application, so all requests will be executed client-side. Unfortunately, In your case that will mean that requests will be blocked. |
Thank you for the clarification. |
|
has this been merged? Alternative end-point to openai would be very helpful to have. |
|
No, would be a breaking change with the current merges, I'd need to redo
the PR myself.
…On Wed, Feb 7, 2024, 1:06 AM Joos Kiener ***@***.***> wrote:
has this been merged? Alternative end-point to openai would be very
helpful to have.
—
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APESZJXBQJUVIDNKRDM6GZDYSMRVVAVCNFSM6AAAAAAWMGK6Z6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZRGQYDSNRSGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I don't think this PR is required anymore. It looks like my changes were copied and merged in e60272e |
5 participants
Added config options, default configuration via a
config.jsonfile, plus support for custom endpoints including Azure OpenAI.Closes #21 and #16