refactor: Use environment variables for backend endpoint

Instead of hardcoding in backend endpoints in the front-end use environemnt variables setup suggest by next.js. Makes it easier to switch endpoints on-the-fly in dev, test prod

Author: johanravn

.nvmrc

@@ -0,0 +1 @@
+v22.9.0

front/.env.development

@@ -0,0 +1 @@
+NEXT_PUBLIC_BACKEND_HOST=http://localhost:5000

front/.env.production

@@ -0,0 +1 @@
+NEXT_PUBLIC_BACKEND_HOST=http://localhost:5000

front/package-lock.json

@@ -1,7 +1,7 @@
 import createAPI from "@/lib/api";
 
 const api = createAPI({
-  baseURL: "http://localhost:5000",
+  baseURL: `${process.env.NEXT_PUBLIC_BACKEND_HOST}`,
   withCredentials: true,
 });
 

front/src/app/api.ts

@@ -4,9 +4,10 @@ import { z } from "zod";
 
 import { GetManySchema } from "@/lib/schemas";
 
-export const HOST = "http://localhost:5000";
+export const HOST = `${process.env.NEXT_PUBLIC_BACKEND_HOST}`;
 export const BASE_ROUTE = `/api/v1`;
 
+
 export const instance = axios.create({
   withCredentials: true,
   baseURL: HOST,

front/src/lib/api/common.ts

@@ -36,7 +36,7 @@ type APIConfig = {
 };
 
 const DEFAULT_CONFIG: APIConfig = {
-  baseURL: "http://localhost:5000",
+  baseURL: `${process.env.NEXT_PUBLIC_BACKEND_HOST}`,
   withCredentials: true,
 };