ESP32-S3 Bench Guide
ESP32-S3 N16R8 bench guide: live pinout, lessons, simulators and the bench log.
A modern way to understand Gita
Translation pending
EducationJavaScript · HTMLGitHub @ayush-sahooOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
The Bhagavad Gita website at gitaverse.co.in: all 18 chapters and 700 verses with meanings in 74 languages, verse narration, and "Ask Krishna", a guide that answers life questions from the Gita. Visitors can ask Krishna one question without an account and one more after a free sign-up; Annual Access (₹1,000/year, paid through Razorpay) unlocks the rest.Read the full README ↗The Bhagavad Gita website at gitaverse.co.in: all 18 chapters and 700 verses with meanings in 74 languages, verse narration, and "Ask Krishna", a guide that answers life questions from the Gita. Visitors can ask Krishna one question without an account and one more after a free sign-up; Annual Access (₹1,000/year, paid through Razorpay) unlocks the rest.
| Read this | For |
|---|---|
| docs/ARCHITECTURE.md | How the site, edge functions and database fit together, and the key flows (sign-in, free question, payment, translations, narration). |
| docs/DEVELOPMENT.md | Running locally, tests, and how to change the website, edge functions, migrations and languages safely. |
| docs/TRACKING.md | Meta Pixel events the ad campaign depends on, and the first-party analytics behind the admin dashboard. |
| docs/OPERATIONS.md | Services, secrets, the admin dashboard, the translation worker, health checks and common tasks. |
| CONTRIBUTING.md | Branches, pull requests and what to check before merging. |
# Run the site (no build step; it talks to the live Supabase project)
python3 -m http.server 8000 # open http://localhost:8000
# Unit tests
node --test tests/*.cjs
# Browser tests (simulated backend; nothing touches production)
cd tests/e2e && npm ci && npx playwright install chromium && node run.mjs
index.html + app.js (plain JavaScript) on Vercel. Merging to main deploys to production.bkwvuckznpaawmqrjjgk (Postgres, Auth, edge functions in supabase/functions/, migrations in supabase/migrations/).index.html, app.js, languages.js, connected.css the website
admin.html owner dashboard
privacy.html, terms.html, refund.html, contact.html, legal.css
policy pages (generated by tools/build_legal_pages.py)
api/geo.js Vercel function: visitor location
supabase/functions/ edge functions (+ _shared/)
supabase/migrations/ database schema, in applied order
supabase/config.toml edge-function settings (JWT verification off)
tests/*.cjs unit tests
tests/e2e/ browser tests and runner
tools/ policy-page generator, translation-piece exporter
loadtest/stress.mjs load test for the public site
.github/workflows/tests.yml CI
App.tsx, src/, app.json, eas.json, package.json earlier Expo app, parked and not deployed
Secrets are never stored in the repo; they live in Supabase (Edge Functions → Secrets). See docs/DEVELOPMENT.md.