Distribute with Warp

[mottosso]

• https://github.com/dgiagio/warp

Gave this a go, and is working well. It's a self-extracting compressed binary, which unpacks itself to a local directory on first-run and re-uses that for subsequent runs.

$ pyblish-qml
# ...unpacking...
# start
$ pyblish-qml
# start

The result is single-file distribution and fast execution, even if it's located on a network drive. Updates are made by replacing the single-exe file with a newer version.

[tokejepsen]

super interesting, not only for pyblish-qml but for distributed pipelines as well.

[mottosso]

Yeah, it's quite simplistic; anything you can put in a folder you can distribute with it. You point it to a folder for zipping, e.g. c:\python36, and the name of an executable inside of it, e.g. python.exe along with arguments, e.g. -m pyblish_qml and it'll hand you a single .exe that takes a little while the first time, but then no more.

Could also work as a more general, shared Python distribution.

//192.168.1.111/mypython36/python.exe

Not sure, but it'd be nice if it also knew when to update the local copy, say if the .exe has been updated.

[tokejepsen]

Not sure, but it'd be nice if it also knew when to update the local copy, say if the .exe has been updated.

I thought it did update? Here's from the readme:

The extraction process only happens the first time the application is ran, or when the self-contained application binary is updated.

[mottosso]

Then that it pretty slick I think. :)

[tokejepsen]

Could be cool if it queried a remote location for updates to the exe as well. That way you could release binaries to GitHub and your distributed users would get the updates.

[mottosso]

Sounds like a PR!