• Auth: Clerk

• App logic: Next.js

• VectorDB: Pinecone / Supabase pgvector

• LLM Orchestration: Langchain.js

• Image Model: Replicate

• Text Model: OpenAI

• Text streamming: ai sdk

• Deployment: Fly

• Quickstart

• Contribute to this repo

plain text
git clone git@github.com:[YOUR_GITHUB_ACCOUNT_NAME]/ai-getting-started.git

plain text
cd ai-getting-started
npm install

plain text
cp .env.local.example .env.local

• Create a Pinecone index by visiting https://app.pinecone.io/ and click on "Create Index"

• Give it an index name (this will be the environment variable PINECONE_INDEX)

• Fill in Dimension as 1536

• Once the index is successfully created, click on "API Keys" on the left side nav and create an API key: copy "Environment" value to PINECONE_ENVIRONMENT variable, and "Value" to PINECONE_API_KEY

• Create a Supabase instance here; then go to Project Settings -> API

• SUPABASE_URL is the URL value under "Project URL"

• SUPABASE_PRIVATE_KEY is the key starts with ey under Project API Keys

• Now, you should enable pgvector on Supabase and create a schema. You can do this easily by clicking on "SQL editor" on the left hand side on supabase UI and then clicking on "+New Query". Copy paste this code snippet in the SQL editor and click "Run".

plain text
npm run generate-embeddings-pinecone

plain text
npm run generate-embeddings-supabase

• Register an account on fly.io and then install flyctl

• Run fly launch under project root -- this will generate a fly.toml that includes all the configurations you will need

• Run fly deploy -ha=false to deploy the app -- the -ha flag makes sure fly only spins up one instance, which is included in the free plan. You also want to run fly scale memory 512 to scale up the fly vm memory for this app.

• For any other non-localhost environment, the existing Clerk development instance should continue to work. You can upload the secrets to Fly by running cat .env.local | fly secrets import

• If you are ready to deploy to production, you should create a prod environment under the current Clerk instance. For more details on deploying a production app with Clerk, check out their documentation here. Note that you will likely need to manage your own domain and do domain verification as part of the process.

• Create a new file .env.prod locally and fill in all the production-environment secrets. Remember to update NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY and CLERK_SECRET_KEY by copying secrets from Clerk's production instance -cat .env.prod | fly secrets import to upload secrets

• Netlify

• Vercel

1. Clcik on Fork on the top right of this page

2. Work on your change and push it to your forked repo. Now when you navigate to the forked repo's UI, you should see something like the following:

1. Click on "Contribute" -> "Open Pull Request".

2. Once you have a PR, you can add reviewers.

• https://js.langchain.com/docs/modules/indexes/vector_stores/integrations/pinecone

• https://js.langchain.com/docs/modules/models/llms/integrations#replicate

• https://js.langchain.com/docs/modules/chains/index_related_chains/retrieval_qa