fix: use NEXT_PUBLIC prefix for DOMAIN env

Since we use it both on client and server, we must do this. An alternative is to compute strings on server side and pass it through API to the client, but that's too overcomplicated for a public available information such as the domain we use

Author: lorenzocorallo

src/env.ts

@@ -8,20 +8,16 @@ export const env = createEnv({
   client: {
     NEXT_PUBLIC_DOMAIN: z
       .string()
-      .describe("Exposed to client side, same as env.DOMAIN"),
+      .default(`polinet.cc`)
+      .describe(
+        "This is the domain to use as shortener. API available at /api and Admin dashboard at /admin"
+      ),
   },
   server: {
     PORT: z.coerce.number().min(1).max(65535).default(PORT),
     NODE_ENV: z.enum(["development", "production"]).default("development"),
     // PUBLIC_URL: z.string().default(`https://polinet.cc`),
     // LOG_LEVEL: z.string().default("DEBUG"),
-    DOMAIN: z
-      .string()
-      .default(`polinet.cc`)
-      .describe(
-        "This is the domain to use as shortener. API available at /api and Admin dashboard at /admin"
-      ),
-
     DB_HOST: z.string().min(1),
     DB_PORT: z.coerce.number().min(1).max(65535).default(5432),
     DB_USER: z.string().min(1),
@@ -32,8 +28,7 @@ export const env = createEnv({
 
   runtimeEnv: {
     PORT: process.env.PORT,
-    DOMAIN: process.env.DOMAIN,
-    NEXT_PUBLIC_DOMAIN: process.env.DOMAIN,
+    NEXT_PUBLIC_DOMAIN: process.env.NEXT_PUBLIC_DOMAIN,
     DB_HOST: process.env.DB_HOST,
     DB_PORT: process.env.DB_PORT,
     DB_USER: process.env.DB_USER,