···11+# flyctl launch added from .gitignore
22+**/node_modules
33+**/dist
44+**/.wrangler
55+**/.dev.vars
66+77+# Change them to your taste:
88+**/package-lock.json
99+**/yarn.lock
1010+**/pnpm-lock.yaml
1111+**/bun.lockb
1212+fly.toml
1313+1414+node_modules
+10
apps/screenshot-service/.gitignore
···11+node_modules
22+dist
33+.wrangler
44+.dev.vars
55+66+# Change them to your taste:
77+package-lock.json
88+yarn.lock
99+pnpm-lock.yaml
1010+bun.lockb
···11+import { createEnv } from "@t3-oss/env-core";
22+import { z } from "zod";
33+44+export const env = createEnv({
55+ server: {
66+ R2_TOKEN: z.string().min(1),
77+ R2_URL: z.string().min(1),
88+ R2_ACCESS_KEY: z.string().min(1),
99+ R2_SECRET_KEY: z.string().min(1),
1010+ HEADER_TOKEN: z.string().min(1),
1111+ },
1212+1313+ /**
1414+ * What object holds the environment variables at runtime. This is usually
1515+ * `process.env` or `import.meta.env`.
1616+ */
1717+ runtimeEnv: process.env,
1818+1919+ /**
2020+ * By default, this library will feed the environment variables directly to
2121+ * the Zod validator.
2222+ *
2323+ * This means that if you have an empty string for a value that is supposed
2424+ * to be a number (e.g. `PORT=` in a ".env" file), Zod will incorrectly flag
2525+ * it as a type mismatch violation. Additionally, if you have an empty string
2626+ * for a value that is supposed to be a string with a default value (e.g.
2727+ * `DOMAIN=` in an ".env" file), the default value will never be applied.
2828+ *
2929+ * In order to solve these issues, we recommend that all new projects
3030+ * explicitly specify this option as true.
3131+ */
3232+ skipValidation: true,
3333+});