Option to configure API key for instance

[zekker6]

For my use-case I'd like to host chatpad in a private space for several users who will have access.
Current implementation is great for privacy and shared deployments for different users, but it's a bit hard to explain non-technical users how to insert their key and configure model for usage.

It would be great if there would be an option to configure an API key which will be used for all users.
For the docker deployment(hoping #8 is getting merged soon :) ) it would be great to have option to define an env variable which will be used for this.

Since this is a static front-end applications I can suggest 2 options to implement this atm:

• to use some bash scripting for docker container startup and embed key value in some special placeholder.
  This option would require to define some variable in code and set a unique value which could be replaced when container will start. While I've used similar approach in the past, and it worked, but it seems to be very hacky way for this.
• to write a key into some file and read it with regular HTTP request served by nginx. Application than can just request key and use it.

Option 2 seems to be less secure than option one, but both options will have a key in plaintext when just browsing source. For my use-case it is safe to have key in plaintext without any authentication since it will only be reachable inside my network, so there is no risk of leaking key to public.

I will be happy to help with scripting/docker setup if this will be implemented and any help will be needed.

[Supernova3339]

hey there 👋
I've been thinking about this for awhile - however I don't have the time to implement it.
The multi user part - not the API key setting.

[GOvEy1nw]

ah that's a shame. That would be fantastic.

[flowjzh]

Similar use case here (dealing with a bunch of recruiters) and this feature would be a big help.

[jremick]

Having a method of saving the API key for the instance, not in the browser, would be great. I'd like to run instances of this on my local server for family/friends as well as use a personal instance across multiple systems/browsers (entering an API key each time is a hassle).

[Supernova3339]

Your exported data contains your API key

…

On Tue, Apr 18, 2023, 4:41 PM Jarel ***@***.***> wrote: Having a method of saving the API key for the instance, not in the browser, would be great. I'd like to run instances of this on my local server for family/friends as well as use a personal instance across multiple systems/browsers (entering an API key each time is a hassle). — Reply to this email directly, view it on GitHub <#21 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APESZJRKLA7MUW5G336ROQDXB4C7DANCNFSM6AAAAAAWELAKUA> . You are receiving this because you commented.Message ID: ***@***.***>

[nrgbistro]

It would also be nice to save chats and prompts to the instance rather than the browser. This would let me access my previous chats I wrote on my desktop from my laptop, similar to how the actual chatGPT frontend works. I guess this also involves user auth in some way to separate each person's chats. Perhaps SSO could be implemented to start?

[Supernova3339]

This is accessable from your data export. Adding accounts adds a database. Chatpad has one, however its browser side and not server side. Feel free to make a PR if you wan to implement this yourself.