0.6.1

⚠️ IMPORTANT: ⚠️

Please update your docker-compose.yml file to include the following changes:

  dawarich_sidekiq:
    image: freikin/dawarich:latest
    container_name: dawarich_sidekiq
    volumes:
      - gem_cache:/usr/local/bundle/gems
+     - public:/var/app/public

Added

• Added a line with public volume to sidekiq's docker-compose service to allow sidekiq process to write to the public folder

Fixed

• Fixed a bug where the export file was not being created in the public folder

Full Changelog: 0.6.0...0.6.1

0.6.0

Added

• Exports page to list existing exports download them or delete them

Changed

• Exporting process now is done in the background, so user can close the browser tab and come back later to download the file. The status of the export can be checked on the Exports page.

ℹ️ Deleting Export file will only delete the file, not the points in the database. ℹ️

⚠️ BREAKING CHANGES: ⚠️

Volume, exposed to the host machine for placing files to import was changed. See the changes below.

Path for placing files to import was changed from tmp/imports to public/imports.

  ...

  dawarich_app:
    image: freikin/dawarich:latest
    container_name: dawarich_app
    volumes:
      - gem_cache:/usr/local/bundle/gems
-     - tmp:/var/app/tmp
+     - public:/var/app/public/imports

  ...

  ...

volumes:
  db_data:
  gem_cache:
  shared_data:
- tmp:
+ public:

What's Changed

• Exports by @Freika in #62

Full Changelog: 0.5.3...0.6.0

0.5.3

Added

• A data migration to remove points with 0.0, 0.0 coordinates. This is necessary to prevent errors when calculating distance in Stats page.

Fixed

• Reworked code responsible for importing "Records.json" file from Google Takeout. Now it is more reliable and faster, and should not throw as many errors as before.

What's Changed

• Bump oj from 3.16.3 to 3.16.4 by @dependabot in #55
• Bump tailwindcss-rails from 2.6.0 to 2.6.1 by @dependabot in #56
• Bump sprockets-rails from 3.4.2 to 3.5.1 by @dependabot in #57
• Bump will_paginate from 4.0.0 to 4.0.1 by @dependabot in #58
• Bump rails from 7.1.3.3 to 7.1.3.4 by @dependabot in #59

Full Changelog: 0.5.2...0.5.3

0.5.2

[0.5.2] — 2024-06-08

Added

• Test version of google takeout importing service for exports from users' phones

Google have announced shifting storage of Google Timeline from their servers to users' mobile devises instead. This release is aimed to implement a first version of importing process that supports files that users can export directly from their devises.

Full Changelog: 0.5.1...0.5.2

0.5.1

Added

• Background jobs concurrency now can be set with BACKGROUND_PROCESSING_CONCURRENCY env variable in docker-compose.yml file. Default value is 10.
• Hand-made favicon

Changed

• Change minutes to days and hours on route popup

Fixed

• Improved speed of "Stats" page loading by removing unnecessary queries

Full Changelog: 0.5.0...0.5.1

0.5.0

[0.5.0] — 2024-05-31

Added

• New buttons to quickly move to today's, yesterday's and 7 days data on the map
• "Download JSON" button to points page
• For debugging purposes, now user can use ?meters_between_routes=500 and ?minutes_between_routes=60 query parameters to set the distance and time between routes to split them on the map. This is useful to understand why routes might not be connected on the map.
• Added scale indicator to the map

Changed

• Removed "Your data" page as its function was replaced by "Download JSON" button on the points page
• Hovering over a route now also shows time and distance to next route as well as time and distance to previous route. This allows user to understand why routes might not be connected on the map.

Full Changelog: 0.4.3...0.5.0

0.4.3

[0.4.3] — 2024-05-30

Added

• Now user can hover on a route and see when it started, when it ended and how much time it took to travel

Fixed

• Timestamps in export form are now correctly assigned from the first and last points tracked by the user
• Routes are now being split based both on distance and time. If the time between two consecutive points is more than 60 minutes, the route is split into two separate routes. This improves visibility of the routes on the map.

Full Changelog: 0.4.2...0.4.3

0.4.2

[0.4.2] — 2024-05-29

Changed

• Routes are now being split into separate one. If distance between two consecutive points is more than 500 meters, the route is split into two separate routes. This improves visibility of the routes on the map.
• Background jobs concurrency is increased from 5 to 10 to speed up the processing of the points.

Fixed

• Point data, accepted from OwnTracks and Overland, is now being checked for duplicates. If a point with the same timestamp and coordinates already exists in the database, it will not be saved.

What's Changed

• Bump chartkick from 5.0.6 to 5.0.7 by @dependabot in #48
• Bump webmock from 3.23.0 to 3.23.1 by @dependabot in #47

Full Changelog: 0.4.1...0.4.2

0.4.1

[0.4.1] — 2024-05-25

Added

• Heatmap layer on the map to show the density of points

What's Changed

• Bump rubocop-rails from 2.24.1 to 2.25.0 by @dependabot in #39
• Bump rails from 7.1.3.2 to 7.1.3.3 by @dependabot in #40

Full Changelog: 0.4.0...0.4.1

0.4.0

[0.4.0] — 2024-05-25

BREAKING CHANGES:

• /api/v1/points is still working, but will be deprecated in nearest future. Please use /api/v1/owntracks/points instead.
• All existing points recorded directly to the database via Owntracks or Overland will be attached to the user with id 1.

Added

• Each user now have an api key, which is required to make requests to the API. You can find your api key in your profile settings.
• You can re-generate your api key in your profile settings.
• In your user profile settings you can now see the instructions on how to use the API with your api key for both OwnTracks and Overland.
• Added docs on how to use the API with your api key. Refer to /api-docs for more information.
• POST /api/v1/owntracks/points endpoint.
• Points are now being attached to a user directly, so you can only see your own points and no other users of your applications can see your points.

Changed

• /api/v1/overland/batches endpoint now requires an api key to be passed in the url. You can find your api key in your profile settings.
• All existing points recorded directly to the database will be attached to the user with id 1.
• All stats and maps are now being calculated and rendered based on the user's points only.
• Default TIME_ZONE environment variable is now set to 'UTC' in the docker-compose.yml file.

Fixed

• Fixed a bug where marker on the map was rendering timestamp without considering the timezone.

• Api Key authentication by @Freika in #42
  Full Changelog: 0.3.2...0.4.0