Loc is a platform for discovering local events in the Netherlands. It collects events from external sources, publishes the ones that meet its quality rules, and lets visitors search, filter and explore them.
Live: loc.shadibuilds.dev
For visitors, no account needed:
- Search events by text, and filter them by city, category, tag, date range, time of day, and in person or online.
- A homepage with rails for tonight, this weekend, near you and online, above the full event list.
- Event pages with the address, map coordinates, images, organizers, every upcoming date and a weather forecast for in-person events.
- Organizer pages with their profile and upcoming events.
For members:
- Registration with email verification, login and logout.
- Save events and follow organizers (through the API).
Behind the scenes:
- Events are collected daily from RVO and Ticketmaster, normalized, tagged and checked against publication rules before anyone sees them.
- Events whose descriptions are long enough are tagged with Gemini.
- Forecasts are fetched for published in-person events.
- Two backend applications, one database. The data application owns ingestion (
catalogschema) and publishes a read contract (publicationschema). The product API only reads that contract and owns its ownappschema. Each app runs its own Flyway history. - Stateless authentication with Spring Security. Short-lived JWT access tokens, plus rotating refresh tokens in an
HttpOnlycookie with reuse detection. Every route is denied unless opened explicitly. - Rate limiting with Redis on registration, login, verification emails and session refresh.
- Consistent errors. Every error response is an RFC 9457
ProblemDetail. - Real integration tests. Backend tests run against real PostgreSQL and Redis containers with Testcontainers.
- CI/CD per application with GitHub Actions, deployed with Docker Compose to a self-hosted server behind Cloudflare Tunnel.
- API documentation with OpenAPI and Scalar at
/api/docs.
Loc consists of three applications:
| Application | Technology | Responsibility |
|---|---|---|
| Backend | Java 25, Spring Boot | Product API: event discovery, user accounts, authentication, saved events, followed organizers |
| Data | Java 25, Spring Boot | Collects external events, normalizes and enriches them, publishes qualified events |
| Frontend | Angular, Tailwind CSS | User interface; talks only to the backend API |
Supporting infrastructure: PostgreSQL, Redis, RabbitMQ and S3-compatible object storage (Cloudflare R2).
RVO, Ticketmaster → Data → PostgreSQL (publication) → Backend API → Frontend
│
└── raw files in Cloudflare R2
The system architecture describes the components and their boundaries.
.
├── backend/ Spring Boot product API
├── data/ Data collection and publication application
├── frontend/ Angular application
├── deploy/ Production deployment script
├── docs/ Cross-system architecture documentation
├── scripts/ Local development scripts
└── screenshots/ Project screenshots
Requirements: Docker, Java 25 and Node.js.
-
Copy
.env.exampleto.envand fill in the values. -
Start the local infrastructure:
docker compose up -d db redis rabbitmq mailpit
-
Start the applications by following their guides:
| Service | Local address |
|---|---|
| Frontend | http://localhost:4200 |
| Backend API | http://localhost:8080/api |
| API documentation | http://localhost:8080/api/docs |
| Mailpit (local email inbox) | http://localhost:8025 |
| RabbitMQ management | http://localhost:15672 |
- System architecture
- Data architecture
- Authentication
- Backend guide, Discovery API, Member API and Event photos
- Data guide
- Frontend guide
- Development scripts
- CI/CD workflows
- Production deployment
Loc started as the HackYourFuture Class 55 Group A final project and is now independently designed and maintained.