Changeset 5f483e3 in Klonkt for .env.example

Timestamp:

06/27/2026 03:01:13 PM (2 months ago)

Author:

Robin Genis <roboburr@…>

Branches:

main

Children:

3746f6a

Parents:

98fe58a

Message:

chore: code cleanup — remove dead files, deps, DB tables, Google-login remnants

• Deleted dead files: routes/notifications.js + services/NotificationService.js + views/pages/notifications.ejs (old bell, unmounted; live fedi notifications live in posts.js); deploy/verify.ps1 (stale smoke test).
• package.json — drop unused ws dependency (no WebSocket since Prutter was removed).
• .env.example — drop GOOGLE_* vars (Google login removed).
• config/database.js — remove CREATE statements for dead tables (circle_links/remote_actors/ remote_posts from old Circles v1; user_notifications; post_likes). No DROP — existing rows stay.
• services/i18n.js — remove dead keys: hub, prutter, and the whole Google-login set (+ the agoog.* wizard + glog.* notices, ~280 lines). Kept aseo.verify_google. solo_desc/login_google_only de-Googled.
• views/pages/auth-login.ejs — drop the dead Google error block + button CSS; the password login form is unchanged.
• deploy/post-receive — fix stale pm2 reload prutcms -> klonkt.

File:

• .env.example (modified) (1 diff)

.env.example

@@ -27 +27 @@
 # `npm run reset-admin` on the server.
 
-# ── Google login for LISTENERS (optional) ───────────────────────────
-# Want listeners to sign in with Google to comment? Create your OWN Google OAuth
-# client (Google Cloud Console -> Credentials -> OAuth client ID -> "Web
-# application") and fill it in below. Your own client = your own Google Cloud
-# project; this site isn't centrally tied to anything. Not set? Then there's
-# simply no Google button. Google login NEVER grants admin rights (commenting only).
-# GOOGLE_REDIRECT_URI = <your domain>/auth/google/callback (set it exactly in the client)
-GOOGLE_CLIENT_ID=
-GOOGLE_CLIENT_SECRET=
-GOOGLE_REDIRECT_URI=https://example.com/auth/google/callback
-
 # ── Email (optional) — for "forgot password" reset links ────────────
 # Not set? Then reset only works via `npm run reset-admin` on the server.