Skip to content
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

fix: use correct config path during development #1690

Merged
merged 2 commits into from
Oct 13, 2020
Merged

Conversation

lidel
Copy link
Member

@lidel lidel commented Oct 9, 2020

This PR makes instance started via npm start read package.json and that makes Electron to use config from ~/.config/IPFS Desktop instead of ~/.config/Electron.

Goal here is to have the same behavior in dev as in packaged production version, reducing the surface for human error (eg. I was removing ~/.config/IPFS Desktop between tests while ~/.config/Electron remained with broken config)

@hacdias @olizilla cc fyi (I remember this being an issue in past, this seems to be the fix)

This makes electron to read package.json and other config correctly,
so configuration is read from ~/.config/IPFS Desktop instead of
~/.config/Electron, so npm start behaves closer to production.

License: MIT
Signed-off-by: Marcin Rataj <[email protected]>
Copy link
Member

@hacdias hacdias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it fixes it, I'm all for it!

@rafaelramalho19
Copy link
Contributor

I think you repeated yourself with "~/.config/IPFS Desktop instead of ~/.config/IPFS Desktop", did you mean:
~/.config/IPFS Desktop instead of ~/.config/Electron ?

@lidel
Copy link
Member Author

lidel commented Oct 13, 2020

@rafaelramalho19 correct – i fixed PR description, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants