Files
zeekayandHanzo Dev 6b68c9299e kv: one name for the store, and it is Hanzo KV
The client was already @hanzo/kv; only the vocabulary was still Redis. Every
module, symbol and comment now says what it connects to:

  lib/redis.ts                    -> lib/kv.ts                (exports kv, lockKv)
  lib/redis-job-store.ts          -> lib/kv-job-store.ts      (KvJobStore)
  lib/redis-download-job-store.ts -> lib/kv-download-job-store.ts
  lib/files/tus-redis-locker.ts   -> lib/files/tus-kv-locker.ts (KvLocker, KvLock)
  lib/api/domains/redis.ts        -> lib/api/domains/kv.ts    (getKey)
  lib/redis/                      -> lib/kv-queue/

KV_URL is now the only endpoint variable — the REDIS_URL fallback and the
redis://localhost default are gone, and the default scheme is kv://, which
@hanzo/kv parses natively (utils/index.js). .env.example gained the KV_URL it
never documented, and lost UPSTASH_REDIS_REST_LOCKER_URL/TOKEN: nothing has read
those since the client changed — the locker opens a second connection to the
same KV, so there is no second endpoint to configure.

The second connection is `lockKv`, not `locker`: both tus routes already have a
local `const locker = new KvLocker(...)`, so naming the client `locker` made the
lock take itself as its own client.

Verified against the repo's own gate (npx tsc --noEmit): 100 errors before and
after, 0 introduced, compared set-wise by file:line:code. Behaviour is untouched
— this is naming, one connection string, and dead config.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-09 10:09:34 -07:00

70 lines
2.1 KiB
TypeScript

import { NextApiRequest, NextApiResponse } from "next";
import { authOptions } from "@/pages/api/auth/[...nextauth]";
import { getServerSession } from "next-auth/next";
import { sendExportReadyEmail } from "@/lib/emails/send-export-ready-email";
import { jobStore } from "@/lib/kv-job-store";
import { CustomUser } from "@/lib/types";
export default async function handler(
req: NextApiRequest,
res: NextApiResponse,
) {
const session = await getServerSession(req, res, authOptions);
if (!session) {
return res.status(401).end("Unauthorized");
}
const { teamId, exportId } = req.query as {
teamId: string;
exportId: string;
};
const userId = (session.user as CustomUser).id;
if (req.method === "POST") {
try {
// Get export job details
const exportJob = await jobStore.getJob(exportId);
if (
!exportJob ||
exportJob.teamId !== teamId ||
exportJob.userId !== userId
) {
return res.status(404).json({ error: "Export job not found" });
}
// Check if user has email
if (!session.user?.email) {
return res.status(400).json({ error: "User email not found" });
}
// Store email notification flag
await jobStore.updateJob(exportId, {
emailNotification: true,
emailAddress: session.user.email,
});
// If job is already completed, send email immediately
if (exportJob.status === "COMPLETED" && exportJob.result) {
await sendExportReadyEmail({
to: session.user.email,
resourceName: exportJob.resourceName || "Export",
downloadUrl: `${process.env.NEXTAUTH_URL}/api/teams/${teamId}/export-jobs/${exportId}?download=true`,
});
}
return res.status(200).json({ success: true });
} catch (error) {
console.error("Error setting up email notification:", error);
return res
.status(500)
.json({ error: "Failed to setup email notification" });
}
}
res.setHeader("Allow", ["POST"]);
return res.status(405).end(`Method ${req.method} Not Allowed`);
}