Reusable environment for indexID + API on the server side and locally.

[DmitriiTsy]

We need a setup that allows anyone to update the index and API key, enabling them to launch Jockey (backend + frontend) for customers in just a few minutes

[DmitriiTsy]

I'm thinking of a 3-steps solution here:

1. Frontend
   Provide two input fields (on the first main screen of Jockey frontend) : IndexID and APIKey.
   When users fill in these fields and press the button, a call will first be made to verify if this combination of IndexID and APIKey exists in Twelve Labs. If it does:
2. Notify the user that verification is complete, and push these keys through a function to the server side.
3. Launch the server container and notify the user that the container is available, allowing them to start chatting

@james-le-twelve-labs Let me know what do you think about this approach here

[james-le-twelve-labs]

@DmitriiTsy The 3-step solution above makes sense to me.

From our meeting last Thursday, @TravisCouture suggested that there should be a way for the user to not launch the server Docker container every time, so let's explore ways to make the 3rd step more efficient.

[DmitriiTsy]

Hey @james-le-twelve-labs, yes. I did some research and I think this will be ideal: For the third step, I’ll set up the service to accept POST requests from the frontend with an index and key, and update the container’s internal state with new variables