How alexandr1830/labs_web works
This is a small Go web app for browsing a catalog of document-like orders. A user opens the listing, optionally searches by title, or follows an order detail route; handlers retrieve in-memory records and render HTML templates. The API server wires routes, repository, templates, and static resources. The README is empty, so the graph reflects only the sampled source and file tree; template contents and browser-side behavior are not inspected.
Main entry points: server.go HTTP server · handler.go Order handlers · repository.go Order repository · main.go Program entry
Components 8
Application entry
- Program entry
lab1/cmd/awesomeProject/main.go
Web layer
- HTTP server
lab1/internal/api/server.go - Order handlers
lab1/internal/app/handler/handler.go - Order listing
lab1/templates/index.html - Order detail
lab1/templates/order.html - Static resources
lab1/resources
Order catalog
- Order repository
lab1/internal/app/repository/repository.go
Other components
- Browser user
Connections 9
- Browser user → HTTP server: requests pages
lab1/internal/api/server.go - Program entry → HTTP server: starts
lab1/cmd/awesomeProject/main.go - HTTP server → Order repository: creates
lab1/internal/api/server.go - HTTP server → Order handlers: constructs
lab1/internal/api/server.go - HTTP server → Order handlers: routes requests
lab1/internal/api/server.go - Order handlers → Order repository: queries
lab1/internal/app/handler/handler.go - Order handlers → Order listing: renders listing
lab1/internal/app/handler/handler.go - Order handlers → Order detail: renders detail
lab1/internal/app/handler/handler.go - HTTP server → Static resources: serves static files
lab1/internal/api/server.go