DB

• day
  • day (e.g. 2023-02-07) UNIQUE
  • planned_amount_coxes (e.g. 2) DEFAULT 0
  • planned_starting_time NULLABLE STRING
  • open_registration DEFAULT true (false e.g. when usi rowing)
• trip
  • day (FK)
  • user_id
  • cox_id NULLABLE (used if person wants to go with specific cox)
  • begin STRING NULLABLE (only used user_id wants to to be a cox)
  • created TIMESTAMP DEFAULT NOW
• user
  • id
  • name UNIQUE
  • is_cox DEFAULT false
  • is_admin DEFAULT false

UI

• Next 7 days as columns

Edge case

• Trip in the morning on usi rowing day
• after N people (/ cox) -> red highlighted -> queue

Fancy

• Every cox can define which boats they use
• Link for specific trip
• Basic auth (with e.g. ekrv) to prevent spam bots? (Or on first login there are 2 input fields: name + e.g. name of "strom")