All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
- Heatmap layer on the map to show the density of points
BREAKING CHANGES:
/api/v1/pointsis still working, but will be deprecated in nearest future. Please use/api/v1/owntracks/pointsinstead.- All existing points recorded directly to the database via Owntracks or Overland will be attached to the user with id 1.
- 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-docsfor more information. POST /api/v1/owntracks/pointsendpoint.- 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.
/api/v1/overland/batchesendpoint 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_ZONEenvironment variable is now set to 'UTC' in thedocker-compose.ymlfile.
- Fixed a bug where marker on the map was rendering timestamp without considering the timezone.
- Docker volume for importing Google Takeout data to the application
- Instruction on how to import Google Takeout data to the application
- Instruction on how to import Google Takeout data to the application
- Add Points page to display all the points as a table with pagination to allow users to delete points
- Sidekiq web interface to monitor background jobs is now available at
/sidekiq - Now you can choose a date range of points to be exported
- Stop selecting
raw_datacolumn during requests toimportsandpointstables to improve performance.
- Rename PointsController to MapController along with all the views and routes
- Add Points page to display all the points as a table with pagination to allow users to delete points
- Stop ignoring
raw_datacolumn during requests toimportsandpointstables. This was preventing points from being created.
- In right sidebar you can now see the total amount of geopoints aside of kilometers traveled
- Improved overall performance if the application by ignoring
raw_datacolumn during requests toimportsandpointstables.
- Now you can import
records.jsonfile from your Google Takeout archive, not just Semantic History Location JSON files. The import process is the same as for Semantic History Location JSON files, just select therecords.jsonfile instead and choose "google_records" as a source.
- Swagger docs, can be found at
https:<your-host>/api-docs
- Cities, visited by user and listed in right sidebar now also have an active link to a date they were visited
- Dark/light theme switcher in navbar is now being saved in user settings, so it persists between sessions
Breaking changes:
This release changes how Dawarich handles a city visit threshold. Previously, the MINIMUM_POINTS_IN_CITY environment variable was used to determine the minimum number of points in a city to consider it as visited. Now, the MIN_MINUTES_SPENT_IN_CITY environment variable is used to determine the minimum minutes between two points to consider them as visited the same city.
The logic behind this is the following: if you have a lot of points in a city, it doesn't mean you've spent a lot of time there, especially if your OwnTracks app was in "Move" mode. So, it's better to consider the time spent in a city rather than the number of points.
In your docker-compose.yml file, you need to replace the MINIMUM_POINTS_IN_CITY environment variable with MIN_MINUTES_SPENT_IN_CITY. The default value is 60, in minutes.
- A test for CheckAppVersion service class
- Replaced ActiveStorage with Shrine for file uploads
ActiveStorage::FileNotFoundErrorerror when uploading export files
- Set Redis as default cache store
- Consider timezone when parsing datetime params in points controller
- Add rescue for check version service class
- Application version badge to the navbar with check for updates button
- Npm dependencies install to Github build workflow
- Footer
- Disabled map points rendering by default to improve performance on big datasets
- Map controls to toggle polylines and points visibility
- Added content padding for mobile view
- Fixed stat card layout for mobile view
- Removed strong_params from POST /api/v1/points
ActiveStorage::FileNotFoundError: ActiveStorage::FileNotFoundErrorerror when uploading export files
You can now use Overland mobile app to track your location.
- Overland API endpoint (POST /api/v1/overland/batches)
You can now specify the host of the application by setting the APPLICATION_HOST environment variable in the docker-compose.yml file.
- Added version badge to navbar
- Added APPLICATION_HOST environment variable to docker-compose.yml to allow user to specify the host of the application
- Added CHANGELOG.md to keep track of changes
- Specified gem version in Docker entrypoint