Update data and config paths to match platform defaults #1047
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
esimkowitz
changed the title
…ron so electron's aux files go into the same place as our files
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Going forward for new installations, config and data files will be stored at the platform default paths, as defined by env-paths.
For backwards compatibility, if the
~/.wavetermorWAVETERM_HOMEdirectory exists and contains valid data, it will be used. If this check fails, thenWAVETERM_DATA_HOMEandWAVETERM_CONFIG_HOMEwill be used. If these are not defined, thenXDG_DATA_HOMEandXDG_CONFIG_HOMEwill be used. Finally, if none of these are defined, the env-paths defaults will be used.As with the existing app, dev instances will write to
waveterm-devdirectories, while all others will write towaveterm.