educornielis-droid/proyecto-pasantia

Purpose and entry point

This is a Go-backed storefront application with server-rendered HTML, browser-side cart/checkout behavior, database-backed product data, and a payment integration. Process startup is in main.go, which likely composes the database and HTTP server layers.

HTTP server and routing

The application’s HTTP boundary is implemented under servidor/. servidor/servidor.go is the likely server/bootstrap layer, while servidor/routes/routes.go centralizes route registration. Request handling is split by domain, notably checkout behavior in servidor/checkout.go.

Paths:

• main.go

• servidor/servidor.go

• servidor/routes/routes.go

Catalog and rendered UI

HTML is delivered from Go templates rather than a separate frontend runtime. The page set covers landing, products, login, checkout, and a not-found response. Templates are paired with static CSS, JavaScript, and images served by the backend.

Paths:

• templates/index.html

• templates/productos.html

• templates/checkout.html

Cart and checkout flow

The client-side purchase flow is split between cart state/UI code and checkout code. Browser JavaScript likely gathers selected products, updates the cart, and submits or redirects into server-side checkout handling. The server checkout component forms the trust boundary where client purchase input should be validated before payment or persistence actions.

Paths:

• static/js/carrito.js

• static/js/checkout.js

• servidor/checkout.go

Payment-service boundary

servidor/sypagoService.go isolates interaction with the SyPago payment service. This is the primary external-service integration and should own provider-specific request construction, credentials, response handling, and failure mapping; route and checkout handlers should depend on it rather than embed payment protocol details.

Paths:

• servidor/sypagoService.go

• servidor/checkout.go

• .env

Persistence layer

Database access is encapsulated in database/database.go; initial or reference data is represented in database/data.sql. The database layer is the boundary for product/catalog and any purchase-related persistence, keeping SQL concerns out of HTTP handlers.

Paths:

• database/database.go

• database/data.sql

Runtime and infrastructure

The material runtime is Go, defined by go.mod and launched through main.go. Deployment requires environment configuration from .env, a reachable database initialized with database/data.sql, and outbound connectivity to the SyPago payment provider. Static assets and templates are repository-hosted and are expected to be served with the application.

Paths:

• go.mod

• .env

• static/css/style.css