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.
Go Daisy scores 118 activities — surfing, trail running, padel, stargazing, sea swimming — against the wind, waves, tides and sky, and tells you what today is good for. Free, ad-free, no account to st
LifestyleTypeScript · PLpgSQLGitHub @mrdamianraffertyOnlineOwner 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
React PWA for WotNow Activity Companion
Translation pending
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
wotnow
React PWA for WotNow Activity Companion
Sync the core backend secrets from .env.local into a CLI-friendly env file (default .env.cli) so one-off Node/TSX scripts pick up the same credentials:
• npm run env:sync -- --from .env.local --to supabase/.env – copy into a different target file.
• Add --all to copy every key instead of the curated subset (SUPABASE_*, MOON_API_KEY, etc.).
The generated file is safe to add to .gitignore; it’s meant for local usage only.Read the full README ↗React PWA for WotNow Activity Companion
Sync the core backend secrets from .env.local into a CLI-friendly env file (default .env.cli) so one-off Node/TSX scripts pick up the same credentials:
npm run env:sync
Options:
npm run env:sync -- --from .env.local --to supabase/.env – copy into a different target file.--all to copy every key instead of the curated subset (SUPABASE_*, MOON_API_KEY, etc.).The generated file is safe to add to .gitignore; it’s meant for local usage only.
New migrations live under supabase/migrations. To ensure the moon cache table exists (required for /api/moon caching), run the latest migrations against your Supabase project:
supabase db push
The migration 202509300003_ensure_moon_cache_schema.sql creates or upgrades public.moon_cache with the columns used by the moon service and adds protective indexes.
The app includes a comprehensive catch logging and validation system for fishing predictions. Key features:
supabase db pushnpm run seed:findr-validation/findr/log to test the catch logging interfacePOST /api/findr/record-impression - Track prediction viewsGET/POST /api/findr/catch-log - Manage catch entriesPOST /api/findr/record-blank-trip - Log unsuccessful tripsSee docs/FINDR_VALIDATION_SYSTEM.md for complete implementation details, database schema, API reference, and usage examples.
See docs/Supabase Snippet Public Schema Column Inventory-2.csv for the complete Supabase database schema reference.
This project uses the following APIs and services: