Easy-to-manage touch screens
Free, open-source touch screens. Guided USB setup, a drag-and-drop editor and local control. Made for Home Assistant.
What to do in San Francisco, Oakland, San Jose and the whole Bay Area this weekend (Oct 16–18): 21 events plus kid-friendly picks, nightlife, free events, and hot- or rainy-day ideas. Updated daily.
LifestyleJavaScript · AstroGitHub @BaxbyteOnlineOwner 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
Repository for Bay Area weekend activity application
Translation pending
Taken from the repository README
Loading the full README.
Read the full README ↗A fast, fun, SEO-first directory of things to do across the San Francisco Bay Area — rebuilt automatically twice a day from dozens of event sources.
What's inside
scripts/scrape/) — AllEvents (30+ cities), SF Funcheap, 19hz (nightlife), Luma, Ferry Building, Stanford / UCSF / SJSU public calendars, plus Ticketmaster & SeatGeek (free keys) and an optional AI reader for news roundups and venue calendars (Cal Academy, SFMOMA, Cobb's, Yoshi's, libraries, parks…). Sites that block automated access (Eventbrite, DoTheBay, SF Station) are respected and left off. Everything is cleaned, de-duplicated, geocoded, placed in real neighborhood boundaries and tagged.scripts/images/) — Wikimedia Commons (real Bay Area places & events) + Pexels, quality-checked and credited (/photo-credits/). A contact sheet of every chosen photo is published to the image-review branch for a quick visual check.scripts/geo/)./explore/) — Leaflet map with clickable regions, filters, and plain-English search (“free kids stuff in Oakland Saturday”), Spin the Bay 🎰, Near me, and a live weather hint./advertise/, /deals/, data/sponsors.json)./data/events.json, and a ready digest builder (scripts/digest/).llms.txt, IndexNow + WebSub pings after every deploy.npm install
npm run scrape # pull live events (needs internet) → data/events.json
npm run dev # http://localhost:4321
npm test # scraper + digest tests
npm run build # static site → dist/
The site is hosted on Vercel (project bayareaweeked, https://bayareaweeked.vercel.app). Vercel rebuilds and publishes on every push to main, including the bot's twice-daily data commits.
SITE_URL (in Vercel and as a GitHub repo variable) only if you want to override it.PEXELS_API_KEY (Settings → Secrets and variables → Actions). A Vercel env var Pexels_API is only checked at build time (pexels-check: line in the Vercel build log). Optional secrets: TICKETMASTER_API_KEY, SEATGEEK_CLIENT_ID (concerts & games), OPENROUTER_API_KEY (AI reader for venue calendars & news roundups).main, then runs the browser test suite on the live site.data/image-review.json (no logos, text-only flyers, off-topic or adult-themed graphics). With an OPENROUTER_API_KEY secret (a normal inference key), the daily job reviews new images with a vision model; without it, new images stay hidden and the listing uses a real venue or genre photo. Listings whose title has masked profanity never show their image.site-audit branch.PUBLIC_GOOGLE_MAPS_API_KEY is set in Vercel (enable the Map Tiles API and restrict the key to your domain).The daily, photo and photo-candidate workflows have a circuit breaker: if a workflow fails 3 times within 24 hours, every further run is skipped until 24 hours after that 3rd failure. To run anyway, use Actions → (workflow) → Run workflow and tick force, or push a commit whose message contains [force-run]. The rule lives in .github/scripts/circuit-breaker.mjs.
Repo variables (Settings → Secrets and variables → Actions → Variables): SITE_URL, SITE_NAME, PUBLIC_SIGNUP_ENDPOINT, PUBLIC_SPONSOR_ENDPOINT, PUBLIC_CONTACT_EMAIL, GOOGLE_SITE_VERIFICATION, BING_SITE_VERIFICATION, INDEXNOW_KEY, OPENROUTER_MODEL, DEPLOY_TARGET.
Repo secrets (all optional): PEXELS_API_KEY, TICKETMASTER_API_KEY, SEATGEEK_CLIENT_ID, OPENROUTER_API_KEY, GOOGLE_INDEXING_SA_JSON.
See .env.example and the guides in docs/: