[tyre]

You could integrate this, but you don't want to send every single asset to them on every deploy, only the changed ones. You should just keep a manifest file of all krakenified images, and only push them up when you add/alter one.

[pbiggar]

Well, there's where the problem is. I want to do a clean build on each deploy, and there will be many devs on many machines building it, so handling it locally isn't really possible. We could handle it by having a DB keep track, but that's not broadly applicable.

I bring this up because kraken is competing with free programs I already have installed. This is something I can do with those programs that I can't with kraken.