Creating an updater for distributed application

[abraham...@gmail.com]

So I'm going to try and create an updater for my node-webkit application. Before I begin though, I wanted to see what everybody else has been doing so I can get some perspective. 

I'm currently thinking of just distributing my unpacked code (node_modules, package.json, source files, and assets) next to a node-webkit executable, and just redressing the "nw.exe / node-webkit.app" to look like my applications executable. That way, when I have some new code published, I could just unzip it and replace those files without having to mess with the executable. Of course, this means I won't be able to update node-webkit...

Anyways, how do you guys handle this? I appreciate any ideas!

[Michael Winser]

I've just started looking into this. The conclusion I reached was that I would need to handle the scenario of needing to upgrade node-WebKit in addition to my code.  I'm probably going to start with a simple "a new version is available" and an installer.  

I'd like to get to a more chrome like seamless update but I'm going to start small. 

I'd be open to collaborating on a more general solution. 

Michael

--
You received this message because you are subscribed to the Google Groups "node-webkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-webkit...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.