-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
retrieves the storage data in any way? #203
Comments
Related: #174 I didn't find a way to actually survive a server restart :( |
Couldn't agree more that a more permanent solution would be preferable. Until then, it's services I'd rather not provide my data too sadly. |
Well that is the idea. Use an external redis, make it permanent, boom, done. I am thinking about creating a rust fork, and adding a few more features, like this one, adding external data providers in the app (like the ICE Portal here in Germany) and so forth. |
And when you restart that one? |
You can configure redis in a way, that redis saves its data to disk, if you really want to. |
While I respect that long term location tracking/logging is out of scope for the project,
I (and seemingly some other users too) personally would like to make the location data rather persistent.
I've so far tried the following ways to retrieve the data:
Memcached way:
API way:
PHP way:
For now, I'm using the chrome + mitmproxy way (it uses mitmproxy as a man in the middle proxy whereby it logs the /fetch.php api responses onto a file through a python script), but this method is 1. a little lengthy and complicated 2. solely sharing is not enough but accessing the shared url on the chrome instance is necessary, so any server-side way solution would be nicer for me. I also expect to know some apis or hooks for this kind of needs if there's any. But anyways a patching idea suffice my needs if modifying the source code is the only way. Thanks for your help.
The text was updated successfully, but these errors were encountered: