-
Notifications
You must be signed in to change notification settings - Fork 0
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
Custom save-location #2
Comments
That's a very reasonable request and I would consider implementing this. There is a workaround: you can pass a path as an argument to Resoday. So far, it was only intended to be used for testing. It is currently not supported as a user-facing feature, so use it on your own risk:
The directory will be used both for data and configuration files. Here's another much-less-likely-to-work-on-Windows workaround. On Unix-like systems Resoday is compliant with XDG Base Directory Specification. Using the Specification, a user on a Unix-like system (e.g. Linux) can override environment variables #!/usr/bin/bash
export XDG_DATA_HOME=...
export XDG_CONFIG_HOME=...
java -jar resoday-release.jar For finding the paths to the directories Resoday uses library I don't know it is possible to override the paths generated for Windows in |
Preliminary work started in branch https://github.com/rybak/resoday/tree/custom-data-dir |
Released in v1.3. |
situationI
Often be out of house for over a week, and since the default save location is appdata, I can't sync that up easily.
But I do use something like Google Drive and therefore could manage a cross-system save-settings thing.
Wanted solution
Not per se other system settings, but definitely the table data and filled-in days be thrown to a file in a location the user can set.
By doing it this way, I can on the main computer point it to
c:/users/documents/info.db
, and on another computer it imports data fromd:/things/resoday/info.db
, and make it still work.So settings are different per computer, but actual calendar data is similar.
The text was updated successfully, but these errors were encountered: