Commit Graph

13 Commits

Author SHA1 Message Date
ca56389a1e seguimos implementando los secretos
All checks were successful
build-and-deploy / filter (push) Successful in 2s
build-and-deploy / build (push) Successful in 10s
build-and-deploy / deploy (push) Successful in 26s
2025-06-09 17:09:54 -06:00
de869de3a7 actualizando uso de secrets en UI
All checks were successful
build-and-deploy / filter (push) Successful in 1s
build-and-deploy / build (push) Successful in 10s
build-and-deploy / deploy (push) Successful in 26s
2025-06-09 16:55:31 -06:00
513c305971 agregada funcionalidad realtime postgress, api y ui. 2025-06-09 16:35:36 -06:00
56a2ad3605 volver a conectar la UI a la API
All checks were successful
build-and-deploy / filter (push) Successful in 1s
build-and-deploy / build (push) Successful in 12s
build-and-deploy / deploy (push) Successful in 33s
2025-06-06 15:23:45 -06:00
b751cb2911 este agent quedo funcionando al 100 en local al menos
All checks were successful
build-and-deploy / filter (push) Successful in 2s
build-and-deploy / build (push) Successful in 48s
build-and-deploy / deploy (push) Successful in 27s
2025-06-06 14:56:44 -06:00
d570eec221 usar https para las peticiones a la api desde la UI
All checks were successful
build-and-deploy / filter (push) Successful in 1s
build-and-deploy / build (push) Successful in 9s
build-and-deploy / deploy (push) Successful in 26s
2025-06-05 02:54:23 -06:00
5f9de85b44 usar el mcp como es 2025-06-04 17:26:27 -06:00
533637ca51 usar el mcp como es 2025-06-04 17:24:26 -06:00
f4430b001a subiendo
Some checks failed
build-and-deploy / filter (push) Successful in 2s
Sync to GitHub / sync (push) Failing after 2s
build-and-deploy / build (push) Successful in 9s
build-and-deploy / deploy (push) Successful in 14s
2025-05-30 16:24:42 -06:00
4690197ca4 arreglado problema de CORS
Some checks failed
build-and-deploy / filter (push) Successful in 2s
Sync to GitHub / sync (push) Failing after 2s
build-and-deploy / build (push) Successful in 10s
build-and-deploy / deploy (push) Successful in 15s
2025-05-30 10:02:11 -06:00
1198bf1ba8 fix base url
Some checks failed
build-and-deploy / filter (push) Successful in 2s
Sync to GitHub / sync (push) Failing after 1s
build-and-deploy / build (push) Successful in 9s
build-and-deploy / deploy (push) Successful in 14s
2025-05-30 02:40:05 -06:00
944f4a1567 url correcta para la conexion a la api de la UI
Some checks failed
build-and-deploy / filter (push) Successful in 2s
Sync to GitHub / sync (push) Failing after 2s
build-and-deploy / build (push) Successful in 10s
build-and-deploy / deploy (push) Successful in 14s
2025-05-30 02:38:19 -06:00
google-labs-jules[bot]
2441fb9066 I've configured the container names and linked the UI to the API.
Here's what I did:
- Added `container_name` for `api` and `ui` services in `docker-compose.yml`.
- Created `ui/src/apiClient.js` to configure the API base URL using the API container name (`http://planilla-api:4000/api`).
- Added `axios` as a dependency to the UI project.
- Ensured UI store files correctly import the new `apiClient.js`.

This will allow your UI to reliably connect to the API service using Docker's internal DNS resolution via container names.
2025-05-30 08:08:59 +00:00