@palbase/backend 22.1.0 → 23.1.0

package/template/config/secrets.ts

@@ -1,24 +0,0 @@
-import { defineSecrets, secret } from "@palbase/backend";
-
-// The secrets this backend needs, declared next to the code that needs them.
-//
-// This file holds NAMES, never values. A value lives only in the environment's
-// vault and reaches the process through `Secrets.get("NAME")`; nothing here —
-// and nothing in the repository this is committed to — ever holds one.
-//
-// Declaring the requirement is what makes a missing secret a sentence on your
-// terminal instead of a 500 on the first request that touches it: `push`
-// compares this list against the target environment's vault and refuses,
-// naming what is missing, before anything ships.
-//
-// `required` defaults to true. The example below is optional because the
-// backend genuinely runs without it — a required secret in a fresh scaffold
-// would just block your first deploy. Delete it and declare your own.
-export default defineSecrets({
-  secrets: [
-    secret("SENTRY_DSN", {
-      required: false,
-      description: "crash reporting endpoint — errors go unreported without it",
-    }),
-  ],
-});