Configurable OpenAI API Base URL

[EdrisT]

Fix for enhancement issue #194

Added option to use custom OpenAI API base URL.

If not configured the default OpenAI API base URL (https://api.openai.com/v1) will be used.

Does not change current behavior of apiKey, i.e if apiKey is already configured it will not have to be re-entered when modifying base URL.

[eleaner]

that's beautiful
could you help me with what would I need to to build and use this version?
until merged

[EdrisT]

@eleaner This fix is in branch fix-#194 of an up to date fork of rishikanthc:main.

To try this version you either clone this specific branch from my github with git:
git clone -b fix-#194 --single-branch git@github.com:EdrisT/Scriberr.git

Or if using Github go to the specific branch of the fork and download it as a zip-file:
https://github.com/EdrisT/Scriberr/tree/fix-%23194#

Installing it, and everything else, except this fix, works exactly the same as if you would have downloaded/cloned rishikanthc:main.

However, I would recommend you wait for an eventual merge so that you dont miss out on other fixes/enhancements coming to rishikanthc:main.

[eleaner]

I did
git clone -b fix-#194 --single-branch https://github.com/EdrisT/Scriberr.git
then build it and - not really there

I have a question

I see you added base URL to LLM tab
but there is also openai in profiles for whisper-1

[EdrisT]

Yes, my PR only addressed being able to use a custom OpenAI compatible endpoint for the summary and chat feature.

I believe the option to use OpenAI API for the transcription is quite new.

I did not really think about the transcription part.
However, implementing the same kind of option for this part shouldn't be much different.

@rishikanthc, what's your opinion on this?

[eleaner]

downloading zip and then building worked but it does not seem to be detecting any models
does it work for you?

[EdrisT]

Yes, it's working for me. Make sure you use the correct base url and have a valid key for your service and that the api is OpenAI compatible.
Im using it to connect to a self-hosted OpenwebUI instance and have to enter the base url as https://openweb.mycloud.******.com/api, instead of using /v1 at the end.

[rishikanthc]

@EdrisT Yes you are right. Transcription using OpenAI API is new.. And yeah adding support for custom base domains for transcription should be easy too.. Would you be able to update your PR with this? If you don't have the time, I can merge this one for the time being and work on adding support for that later.. I don't see that as a priority right now..
Let me know and I can accordingly merge this or wait.

[EdrisT]

@rishikanthc I'll try to find time to take a look at this. But this is not really a high priority for me either.

I think if you merge this one, the other one can be a separate PR later on.