Age | Commit message (Collapse) | Author | Lines |
|
|
|
got lost in 1.30.0
|
|
some odds and ends left to polish, but ready for testing
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
that should be sufficient…
|
|
|
|
|
|
|
|
(yes, there are actually spambots flooding people with unsolicited
registration e-mails)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes #19
|
|
|
|
Closes #12
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Closes #6
|
|
|
|
Closes #5
|
|
|
|
Whether a user is in transit or not is now determined by an entry in the
in_transit table instead of a dangling checkin.
All completed journeys are stored in the "journeys" table.
This does most of the work needed for automatic checkout. However, note that
the corresponding worker process is not implemented yet.
|