Tikera is split into two independently runnable processes that communicate over HTTP. The frontend is a React single-page application bundled by Vite; it talks to a Laravel API server that reads and writes to a local SQLite database. All authentication is handled through Laravel Sanctum bearer tokens, which the frontend stores inDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/raczkodavid/Tikera/llms.txt
Use this file to discover all available pages before exploring further.
localStorage and attaches to every protected request.
Layer overview
| Layer | Technology | Role |
|---|---|---|
| Frontend | React 19, Redux Toolkit, Tailwind CSS + DaisyUI | SPA served from Vite dev server or static host |
| Backend | Laravel, Laravel Sanctum | RESTful JSON API; handles auth, validation, business logic |
| Database | SQLite | Single-file relational store managed through Laravel migrations |
Client routes
The React application usesreact-router-dom v7 and defines five top-level routes in App.jsx:
| Path | Component | Access |
|---|---|---|
/ | MoviesPage | Public |
/login | LoginPage | Public |
/register | RegisterPage | Public |
/bookings | BookingsPage | Authenticated |
/adminpage | AdminPage | Admin only |
API base URL
The axios instance reads its base URL from theVITE_API_URL environment variable, which is set in the client’s .env file before running the Vite dev server:
api.js this becomes:
vite.config.js) keep imports short across the frontend:
Explore further
Frontend architecture
React component structure, Redux slices, and the service layer
Backend API and models
Laravel controllers, Eloquent models, and database schema