Events stored in the database instead of YAML files - first draft

[kcomandich]

Move events from a YAML file to the database, and provide a way to create/edit/delete events

There are a few remaining items to finish before it's ready to use, but I wanted to make sure I'm on the right track.

See discussion on #342. Implementation so far:

• 1. Create an ApplicationRecord class DatabaseEvent (but use the events db table)
• 2. Update the User class to add :meetup_admin scope
• 3. Data migration & import from yaml file
• 4. Clone the relevant views, except they’re populated from events table instead of yaml
• 5. Add "Edit" button to meetup Event page to a form for updating the Event (ex. https://melbourne.ruby.org.au/events/2026-05-28-ruby-melbourne)
• 6. Add "Add Event" button to meetup Events page (ex. https://melbourne.ruby.org.au/events) to a form for adding a new Event
• 7. Create new events in the events table using the CRUD
• 8. Check if it's all working - compare old views with new views (but see below for new changes)
• 9. Replace the old views with the new views
• 10. Delete old Event class
• 11. Rename DatabaseEvent to Event

Note that UUIDs from the events.yml file don't appear to be used, LMK if they should be.

Still to do/fix:

• Need ability to add/edit/delete Talks in the UI
• Incorporate recent code changes - tabs for past/upcoming events, etc
• In the Melbourne views, filter by region and event_type
• fix: HTML is showing up in the description when saving it
• Remove the date field and create a date method that just uses start_time (no need to have duplicate date and start_time fields)
• Need ability to add/edit Venues in the UI

Thanks to @mcgain for advising! 🙏 🎉

Screenshots:

Clone of the Melbourne event/show page, using events table, with Edit and Delete buttons:

---

New/Edit Event form:

---

Clone of the Melbourne events page, using events table, with New button:

---

Clone of the Melbourne home page, using events table:

[kcomandich]

Copied this from the main site because we now need the lexxy styles for editing the description field in the Melbourne site, and the styles are not shared.

[mcgain]

Bunch of nit-picking sorry, but they are worth addressing

[mcgain]

I think because we're using all here and not all_by_date that the returned event might not actually be the next one. I think all will just return in database insertion order, then today_or_in_the_future? will ensure it's upcoming, but not necessarily the next one by date.

In reality, it is likely that events will be added in the correct order, but if a newer event were to be added, then we'd end up displaying the wrong one.

I suspect this used to be fine, because the yaml events would be ordered by date, but that's not necessarily true of the db.

This is also true of past

[mcgain]

This isn't super important to fix in this PR. It'll be fine in the short term, can be fixed in a followup IMO

[mcgain]

This overrides the ActiveRecord method last, which when given no argument, returns only a single object, rather than an array. Here, we're always returning an array and so break user expectations of the api.

Also, this is probably susceptible to the same issue as upcoming, so an all_by_date is probably necessary here and might allow you to avoid the reverse.

[mcgain]

one more