Open DmitriiTsy opened 2 weeks ago
I'm thinking of a 3-steps solution here:
@james-le-twelve-labs Let me know what do you think about this approach here
@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.
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
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