Pre-launch — Gluecron is in final validation. Public signups and git hosting for non-owner users open after launch review.
CodeIssuesDiscussionsWikiPull RequestsProjectsCommitsActionsReleasesContributorsPulse● GatesSecuritySettingsDeploymentsPipelineInsightsAgents✨ Explain✨ Ask AI✨ Workspace✨ Spec✨ Tests▓ Debt Map✨ NL Search🏛 Archaeology
claude/adoring-hopper-5x74bqclaude/affectionate-feynman-ykrf1hclaude/architecture-audit-design-wxprenclaude/build-status-update-3MXsfclaude/charming-meitner-mllb5rclaude/compare-gate-gluecron-s4mFQclaude/confident-faraday-tikcwbclaude/continue-work-XMTlIclaude/crontech-gluecron-deploy-7MIECclaude/crontech-platform-setup-SeKfwclaude/design-2026claude/ecstatic-ptolemy-jMdigclaude/enhance-github-integration-QNHdGclaude/fix-aa-loop-issue-PonMQclaude/fix-actions-and-processclaude/fix-desktop-errors-XqoW8claude/fix-red-workflowsclaude/fix-website-access-6FKJNclaude/gatetest-integration-hardeningclaude/github-audit-improvements-bDFr9claude/gluecron-launch-status-FoMRlclaude/hopeful-lamport-olfCTclaude/issue-to-pr-and-protectionsclaude/jolly-heisenberg-2sg1Qclaude/launch-preparation-QmTb6claude/new-session-xk1l7claude/plan-platform-architecture-kkN4yclaude/platform-analysis-roadmap-1nUGLclaude/platform-launch-assessment-8dWV8claude/polish-platform-release-AeDrUclaude/resume-previous-work-KzyLwclaude/review-crontech-handoff-qYEVqclaude/review-project-completeness-lHhS2claude/review-readme-docs-ulqPKclaude/serene-edison-rj87weclaude/setup-multi-repo-dev-BCwNQclaude/ship-fixes-and-tests-Jvz1cclaude/site-audit-competitive-pctlwgclaude/site-migration-vercel-XstpKclaude/standalone-product-repos-XHFTDcopilot/feat-smart-empty-states-keyboard-first-enhancementcopilot/feat-smart-morning-digest-review-context-restorecopilot/fix-and-process-workflowscopilot/update-ai-powered-code-reviewfeat/debt-mapfeat/push-policy-codeowners-hardeningfeat/smart-digest-contextfeat/stage-impactfeat/t1-secret-migrationfeat/u-polishfeat/w-self-hostfeat/w2-claude-configfix/agent-journey-orphan-sweepgatetest/auto-fix-1776586424172gatetest/auto-fix-1776586534814gatetest/auto-fix-1776590685143gatetest/auto-fix-1776590808199mainops/redeploy-retriggerstyle/dxt-cta-themeworktree-agent-a3377aad30d55da26worktree-agent-a7ef607b7ee1d6c74
reset-admin-password.ts2.8 KB · 91 lines
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
/**
 * Reset (or create) the site admin's password.
 *
 * Use this when you have shell access to the deployment but have lost the
 * site-admin password. Idempotent: if the user exists, updates the password
 * hash; if not, creates the user. Either way, ensures the user is in
 * `site_admins` so they bypass the bootstrap-rule chicken-and-egg.
 *
 * Run against the live database via:
 *
 *     bun run scripts/reset-admin-password.ts <username> <email> <password>
 *
 * On Fly.io that looks like:
 *
 *     fly ssh console -C "bun run scripts/reset-admin-password.ts admin you@example.com 'new-password'"
 *
 * Requires DATABASE_URL set in the environment (which is true inside the
 * Fly machine; locally you'd export it first).
 *
 * Password is bcrypt-hashed with the same parameters as `src/lib/auth.ts`
 * (cost 10). Plaintext is never persisted or logged.
 */

import { db } from "../src/db";
import { users, siteAdmins } from "../src/db/schema";
import { eq, or } from "drizzle-orm";
import { hashPassword } from "../src/lib/auth";

function usage(): never {
  console.error(
    "Usage: bun run scripts/reset-admin-password.ts <username> <email> <password>"
  );
  process.exit(2);
}

const [, , username, email, password] = process.argv;

if (!username || !email || !password) usage();
if (password.length < 8) {
  console.error("Password must be at least 8 characters.");
  process.exit(2);
}
if (!email.includes("@")) {
  console.error("Email looks invalid (no @).");
  process.exit(2);
}

const passwordHash = await hashPassword(password);

// Find by username OR email — either uniquely identifies an existing user.
const existing = await db
  .select({ id: users.id, username: users.username, email: users.email })
  .from(users)
  .where(or(eq(users.username, username), eq(users.email, email)))
  .limit(1);

let userId: string;
let action: "updated" | "created";

if (existing.length > 0) {
  const row = existing[0]!;
  userId = row.id;
  await db
    .update(users)
    .set({ passwordHash, email, username, updatedAt: new Date() })
    .where(eq(users.id, userId));
  action = "updated";
  if (row.username !== username || row.email !== email) {
    console.log(
      `(Note: existing user matched on ${row.username === username ? "username" : "email"}; username/email fields realigned to the values you passed.)`
    );
  }
} else {
  const inserted = await db
    .insert(users)
    .values({ username, email, passwordHash })
    .returning({ id: users.id });
  userId = inserted[0]!.id;
  action = "created";
}

// Ensure site-admin row so we don't depend on the oldest-user bootstrap rule.
await db
  .insert(siteAdmins)
  .values({ userId })
  .onConflictDoNothing({ target: siteAdmins.userId });

console.log(
  `OK — ${action} user "${username}" <${email}> and ensured site_admins row.`
);
console.log(`Sign in at /login with username "${username}".`);