EventRadar is a calendar of sports events. Events can be created, edited and categorized based on their sports. This is an exercise project for a job application.
The video tour is available at https://youtu.be/o6BD1CKfI9k
The web app used to run on Heroku but since the free tiers were removed, the app is no longer available to use in public
The objective is to implement a calendar for sport events. Events may be added to the calendar and it should be possible to categorize the events based on sports.
- Sat., 18.07.2019, 18:30, Football, Salzburg – Sturm
- Sun., 23.10.2019, 09:45, Ice Hockey, KAC - Capitals
Start with identifying the database entities and then create a suitable database diagram (ERD). The ERD should cover all tables and their relations. Furthermore the database should contain additional information, which may be valuable for Sport Calendar.
Create a database following the structure of your ERD. Add all necessary fields to the tables. Foreign keys should be named with a ‘_’ as prefix (Example: _FOREIGNKEY).
Create a HTML frontend to display the data in a user friendly way. Navigation should be indicated but no functionality is needed. Then go on with the PHP part for dynamic display of data – avoid SQL queries within loops!
- Database connection
- SQL query
- Data output
Additional filters can be added to the calendar presentation.
This application uses PHP Symfony, MySQL and XAMPP.
Clone the repository and import the DB export from the directory db-export
into your MySQL database. Set the database path and user credentials in .env
.
Run composer install
(an additional composer update
might be necessary).
To launch the webshop run php bin/console server:run
and then follow the instructions in the terminal.
You can register a new user or use the following existing user account:
[email protected]
for a regular user. The account password is123123
This section describes the steps from the concept to the final implementation of EventRadar.
The following database model was constructed based on the requirements.
Based on the database model and the requirements, the following sitemap and wireframes for the UI are drawn up.
The following screenshots show the final implementation of the user interface.