Rupak Ganguly rupakg

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

Bootstrap v5 Cheat Sheet:

This cheat sheet provides a comprehensive overview of the Bootstrap v5 CSS framework, including its layout system, typography, colors, components, utilities, JavaScript plugins, customization options, accessibility considerations, responsive utilities, and RTL support.

It also demonstrates with some code usage examples how to use various features in your HTML and CSS code.

1. Layout

Container: .container, .container-fluid, .container-{breakpoint}
Grid system: .row, .col, .col-{breakpoint}-{size}
Responsive breakpoints: sm, md, lg, xl, xxl

https://stackoverflow.com/questions/48993286/is-it-possible-to-route-traffic-to-a-specific-pod?rq=1

You can guarantee session affinity with services, but not as you are describing. So, your customers 1-1000 won't use pod-1, but they will use all the pods (as a service makes a simple load balancing), but each customer, when gets back to hit your service, will be redirected to the same pod.

Note: always within time specified in (default 10800):

AMAZON API GATEWAY REGIONS

US East (Ohio) us-east-2 apigateway.us-east-2.amazonaws.com HTTPS ZOJJZC49E0EPZ

US East (N. Virginia) us-east-1 apigateway.us-east-1.amazonaws.com HTTPS Z1UJRXOUMOOFQ8

US West (N. California) us-west-1 apigateway.us-west-1.amazonaws.com HTTPS Z2MUQ32089INYE

US West (Oregon) us-west-2 apigateway.us-west-2.amazonaws.com HTTPS Z2OJLYMUO9EFXC

Story: Writing Scripts with Go

This is a story about how I tried to use Go for scripting. In this story, I’ll discuss the need for a Go script, how we would expect it to behave and the possible implementations; During the discussion I’ll deep dive to scripts, shells, and shebangs. Finally, we’ll discuss solutions that will make Go scripts work.

Why Go is good for scripting?

While python and bash are popular scripting languages, C, C++ and Java are not used for scripts at all, and some languages are somewhere in between.

	[1] Open https://console.cloud.google.com/ with your gmail account

	[2] Create a Project / Choose a Project you have access to.

	[3] Activate "Cloud Shell"

	[4] Prepare a GKE cluster using
	https://istio.io/latest/docs/setup/platform-setup/gke/

	export PROJECT_ID=`gcloud config get-value project` && \

	<!DOCTYPE NETSCAPE-Bookmark-file-1>
	<!-- This is an automatically generated file.
	It will be read and overwritten.
	DO NOT EDIT! -->
	<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-8">
	<TITLE>Bookmarks</TITLE>
	<H1>Bookmarks</H1>
	<DL><p>
	<DT><H3 ADD_DATE="1576816453" LAST_MODIFIED="1578776782">CKAD</H3>
	<DL><p>

	docker container id - 8c37a950839a


	# 1. Copy Mongo dump to container folder
	(Local System)$ docker cp dump/reaction 8c37a950839a:/var/backups/reaction

	# 2. Connect to mongodb docker container
	(Local System)$ docker exec -it 8c37a950839a /bin/bash

	# 3. Check if backup is copied to docker container

	# GraphQL query
	mutation batchDelete($a:ID $b:ID $c:ID $d:ID $e:ID) {
	a:deleteItem(input:{ id:$a }) { id }
	b:deleteItem(input:{ id:$b }) { id }
	c:deleteItem(input:{ id:$c }) { id }
	d:deleteItem(input:{ id:$d }) { id }
	e:deleteItem(input:{ id:$e }) { id }
	}

	# Query variables

	#!/usr/bin/env node
	/* eslint-disable no-console */
	const path = require('path');
	const fs = require('fs');

	const templateFile = path.join(__dirname, '../../serverless.templates.yml');
	const projectFile = path.join(__dirname, '../../serverless.project.yml');
	const profileFile = path.join(__dirname, `../../serverless.project.${process.env.AWS_PROFILE}.yml`);
	const slsFile = path.join(__dirname, '../../serverless.yml');