- Aug 20, 2023
-
-
Birte Kristina Friesel authored
-
- Jul 10, 2023
-
-
Birte Kristina Friesel authored
-
- Jun 04, 2023
-
- May 07, 2023
-
- Mar 31, 2023
-
-
Birte Kristina Friesel authored
-
- Feb 04, 2023
-
- Dec 28, 2022
-
-
Birte Kristina Friesel authored
-
- Dec 26, 2022
-
-
Birte Kristina Friesel authored
-
- Nov 12, 2022
-
- Aug 04, 2022
-
- Jul 14, 2022
-
- Sep 12, 2021
-
-
Birte Kristina Friesel authored
-
- Dec 13, 2020
-
- Feb 01, 2020
-
- Dec 14, 2019
-
-
Birte Kristina Friesel authored
-
- Nov 14, 2019
-
- Oct 30, 2019
-
- Jun 19, 2019
-
-
Birte Kristina Friesel authored
-
- May 19, 2019
-
-
Birte Kristina Friesel authored
-
- May 18, 2019
-
- May 12, 2019
-
- May 11, 2019
-
-
Birte Kristina Friesel authored
-
- May 09, 2019
-
- May 06, 2019
-
-
Birte Kristina Friesel authored
-
- May 04, 2019
-
-
Birte Kristina Friesel authored
-
- May 02, 2019
-
- Apr 26, 2019
-
-
Birte Kristina Friesel authored
-
- Apr 23, 2019
-
-
Birte Kristina Friesel authored
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.
-
- Mar 19, 2019
-
-
Birte Kristina Friesel authored
-
- Mar 08, 2019
-
-
Birte Kristina Friesel authored
-
- Mar 07, 2019
-
-
Birte Kristina Friesel authored
-