Closed Seanmclem closed 1 year ago
The server-side code for self-hosting should be up in the next few days, and will include other options for authentication.
The server-side code for self-hosting should be up in the next few days, and will include other options for authentication.
Cool thanks, but what is the additional authentication for? Like, saving chat history or something else.
Right now login is for saving and syncing your chat history between devices. If you don’t need that, it isn’t required. For self-hosting, you can just deploy the web app without a server and it will work fine (except for the “share chat” button, which needs a database).
Future versions of the self-hosted server will also add (optional) support for running API calls on your server instead of in the browser, using an API key from an environmental variable, which some people might prefer.
Right now login is for saving and syncing your chat history between devices. If you don’t need that, it isn’t required. For self-hosting, you can just deploy the web app without a server and it will work fine (except for the “share chat” button, which needs a database).
Future versions of the self-hosted server will also add (optional) support for running API calls on your server instead of in the browser, using an API key from an environmental variable, which some people might prefer.
Nice. Is there a database where they'd be synced? I set up my own? Or something else already configured
I added the server code for reference - still working on better documentation.
It uses a SQLite database by default.
The example uses auth0 for login. Can there be an example in the readme regarding