An old project I did - A web app for bdo item storage and analysis with real-time price tracking and custom notifications.
Find a file
2025-03-20 14:09:19 +01:00
Cache session lifetime of 10 years 2025-03-09 11:51:19 +01:00
Config Zwischenpush vorbereitung Pricehistory abrufen 2025-02-12 14:32:57 +01:00
Controller bug: fixed various issues from the js restructuring 2025-03-20 08:33:26 +01:00
db pricehistory alle items 💀 ich bin am ende 2025-02-17 16:43:31 +01:00
Engine chore: refactored linkhandling in latte 2025-03-19 15:56:47 +01:00
Model doc: added phpdoc for models 2025-03-19 15:56:47 +01:00
Repository doc: added phpdoc for services 2025-03-20 14:09:19 +01:00
Resources bug: fixed various issues from the js restructuring 2025-03-20 08:33:26 +01:00
Service doc: added phpdoc for services 2025-03-20 14:09:19 +01:00
Util refactor: improved functionality of debug.php 2025-03-19 15:56:47 +01:00
vendor errorhandling 2025-02-19 13:28:12 +01:00
View chore: refactored linkhandling in latte 2025-03-19 15:56:47 +01:00
.gitignore doc: added phpdoc for models 2025-03-19 15:56:47 +01:00
composer.json errorhandling 2025-02-19 13:28:12 +01:00
composer.lock Menu & routing & andere api für markt-daten 2025-02-10 16:12:15 +01:00
index.php chore: removed logginghelper for rewrite 2025-03-19 15:56:12 +01:00
README.md Update README.md 2025-03-19 15:56:47 +01:00

🚀 Overview

A web project for storing and analyzing items, including price development, search, notifications, and automatic API synchronization.

📝 To-Do List

🛠️ Authentication & User Sessions

  • Set up login and session system
    • Users can log in and remain logged in
    • Stored data (e.g., pinned items) is user-specific
  • Enable registration (if necessary)
    • Users can register
    • Passwords are hashed (bcrypt or similar)
  • Session handling for logged-in users
    • Sessions are deleted upon logout
    • Security measures (token, CSRF protection, etc.)

📂 Database & API

  • CHECK IF MULTICURL IS EVEN NECESSARY BECAUSE HERE states "If multiple ids are given..."
  • Store items in the database (all data except price information)
  • Retrieve and store all items from the API
  • [ ] Clear the database beforehand to have a fresh data basis
  • Retrieve and store prices for each item using the ID
  • Store the highest pre-order price and the lowest seller price
  • Store images (as text in the DB or as files in the cache directory for load time optimization)
  • Revise ApiDataRepository
    • Revision → Separate APIs into individual repositories

📊 Price Calculation & Display

  • Dropdown for price overview:
    • On the homepage - [] On detail pages
  • Determine daily item throughput
    • How many items are listed daily?
    • How many items are sold daily?
  • Price forecasts based on historical trends
    • Estimation for price changes in the coming days (only meaningful with sufficient data)

🏠 Homepage & Pinned Items

  • Homepage for logged-in users
    • Displays personalized data
    • Includes a list of pinned items
  • Pin items and remove them
    • Users can pin items
    • Pinned items remain stored in the database
    • Individual pinned items per user

🔍 Search & Navigation

  • Search function to directly find items
  • Main menu with categories for better overview

🔔 Notifications

  • Set up notification system
  • Customizable notifications for each item
    • Bell icon on the item page
    • Popup/banner to select criteria for notifications (price, availability, etc.)

📈 Detail Page with Graphs

  • Create item detail page
    • Graphically display price development

🔄 Automatic Updates & AJAX

  • Call API every few seconds
  • Automatically update data

🔧 Architecture & Structure

  • Refactor individual classes and files

    feat: Features. doc: Documentation. fix: Bug fixes. bug: Bug-related fixes or attention. style: Styling changes. perf: Performance improvements. test: Tests. chore: Chores like refactoring, dependency updates, and routine changes. ci: Continuous integration. misc: Miscellaneous changes.