fix: use relative api path in production
All checks were successful
Build and Deploy / build-and-push (push) Successful in 2m24s
All checks were successful
Build and Deploy / build-and-push (push) Successful in 2m24s
This commit is contained in:
@@ -1,9 +1,10 @@
|
|||||||
|
|
||||||
import { Attendance, DashboardFilter, User } from '../types';
|
import { Attendance, DashboardFilter, User } from '../types';
|
||||||
|
|
||||||
// URL do Backend que criamos (backend/index.js)
|
// URL do Backend
|
||||||
// Certifique-se de rodar o backend com 'node backend/index.js'
|
// Em produção (import.meta.env.PROD), usa caminho relativo '/api' pois o backend serve o frontend
|
||||||
const API_URL = 'http://localhost:3001/api';
|
// Em desenvolvimento, aponta para o localhost:3001
|
||||||
|
const API_URL = import.meta.env.PROD ? '/api' : 'http://localhost:3001/api';
|
||||||
|
|
||||||
export const getAttendances = async (tenantId: string, filter: DashboardFilter): Promise<Attendance[]> => {
|
export const getAttendances = async (tenantId: string, filter: DashboardFilter): Promise<Attendance[]> => {
|
||||||
try {
|
try {
|
||||||
|
|||||||
Reference in New Issue
Block a user