You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The system was original written using a Google Calendar as the primary storage of events. It used to be that users would add events first to the Google Calendar, then import them into inRoads.
This is starting to be a bit of a hassle now that we're starting to write automated testing. Also, our users now come to the inRoads web interface to add events, instead of adding them manually to the Google Calendar.
We should modify the system so that the local mysql database of events is the primary storage. Publishing the events to a Google Calendar should be optional.
The text was updated successfully, but these errors were encountered:
inghamn
changed the title
Use local database primary source of events
Use local database as primary source of events
Jun 18, 2018
The system was original written using a Google Calendar as the primary storage of events. It used to be that users would add events first to the Google Calendar, then import them into inRoads.
This is starting to be a bit of a hassle now that we're starting to write automated testing. Also, our users now come to the inRoads web interface to add events, instead of adding them manually to the Google Calendar.
We should modify the system so that the local mysql database of events is the primary storage. Publishing the events to a Google Calendar should be optional.
The text was updated successfully, but these errors were encountered: