oghliner.deploy is a footgun about oghliner

[delapuente]

• make oghliner.offline generate a checksum or other artifact from the set of files being offlined, then make oghliner.deploy verify the checksum and fail if it doesn't match the one generated by oghliner.offline.

This is already the case so maybe we could use that as a lock (I'm thinking of adding a .version file with the digest) to stop the offline process to work unnecessary but my concern is if this work we are saving worth the effort as the only remaining step is to write to disk (though it could be reason enough).

[mykmelez]

This is already the case so maybe we could use that as a lock (I'm thinking of adding a .version file with the digest) to stop the offline process to work unnecessary but my concern is if this work we are saving worth the effort as the only remaining step is to write to disk (though it could be reason enough).

It might not be worth the effort merely to avoid re-generating an up-to-date worker on offline. But it is surely worth the effort to avoid deploying an out-of-date worker on deploy!

[delapuente]

Sure, I realized that case later!