Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.env example or description #3

Open
shynsky opened this issue Mar 5, 2023 · 5 comments
Open

.env example or description #3

shynsky opened this issue Mar 5, 2023 · 5 comments

Comments

@shynsky
Copy link

shynsky commented Mar 5, 2023

Could someone provide a template/structure for the .env file? It seems like we need: LCC_ENDPOINT_URL and LCC_TOKEN which I don't know where to find.

@Sameedahmad
Copy link

Sameedahmad commented Mar 6, 2023

And I also have no clue what it is, someone needs to guide us here.

@altafr
Copy link

altafr commented Mar 25, 2023

same problem here

@SangeethaVenkatesan
Copy link

LCC_ENDPOINT_URL - This refers to LANGCHAIN CHAT ENDPOINT - which is the backend code - that gets triggered based on the request from next JS. see api/chat.js -

const response = await fetch(process.env.LCC_ENDPOINT_URL, { method: "POST", headers: { "Content-Type": "application/json" }, body: output, });

This is the backend fetch URL - which can be implemented on your own or using https://github.com/hwchase17/chat-langchain

@rdancer
Copy link

rdancer commented Apr 26, 2023

@SangeethaVenkatesan

Suppose one installs https://github.com/hwchase17/chat-langchain and runs it on the same machine. Then .env would be what?:

LCC_ENDPOINT_URL=?what?
LCC_TOKEN=?what?

@rmrfxyz
Copy link

rmrfxyz commented Jul 25, 2023

I assume it's about auth detail for (some) chains, such as here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants