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

Implementing an internal update mechanism #278

Closed
Neltherion opened this issue Nov 24, 2018 · 2 comments
Closed

Implementing an internal update mechanism #278

Neltherion opened this issue Nov 24, 2018 · 2 comments

Comments

@Neltherion
Copy link

@Neltherion Neltherion commented Nov 24, 2018

Hi,

Is there any plans to implement a mechanism for managing updates internally? The way I see it, right now we have to download the binary each time there's a new change, right?

Thanks for the awesome app!

@Neltherion Neltherion changed the title Implementing a continuous update mechanism Implementing an internal update mechanism Nov 24, 2018
@GitSquared
Copy link
Owner

@GitSquared GitSquared commented Nov 24, 2018

Currently there is the updateChecker module that will spawn a message if a newer version has been detected on GitHub Releases.

I thought about including auto-updating a while back (see #98), but didn't think it would be worth it, mostly because i was planning to release eDEX as a finished software, patch up a few bugs post-release and then just never touch the thing again.

That said, seeing how things have spiraled out of control since last Tuesday, an automatic updater might actually be an interesting feature. I'll keep this one on the ever-expanding roadmap.

@GitSquared
Copy link
Owner

@GitSquared GitSquared commented Dec 28, 2018

@GitSquared GitSquared closed this Dec 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants