auto update counterpartyd on script run by default (via git)

[robby-d]

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[ghost]

Does that mean counterpartyd server would autoupdate every time it is executed?

1. If the goal is to avoid unplanned downtime to forced upgrades, that probably wouldn't be frequent enough (although it'd be better than nothing for those who want to auto-update).
2. A configuration parameter like autoupdate=yes|no (the default could be yes) would be a better way to state one's preference for that purpose. Some users may not want to auto-update.
3. Auto updates would auto-break all non-supported OS like Debian or 64-bit Windows because on those systems setup.py may not work out-of-box.

[robby-d]

1. agreed...but it's better in most cases than nothing at all. we can look into more elegant solutions later
2. yes, agreed (was planning on doing this but I thought you were psychic, Sean 🎱 ) :)
3. yes...I can only have this functionality with federated nodes, at least at first, I'm thinking...

[ghost]

Related to this - I just looked at the part of FN setup script and how it checks if FN was deployed on the same node before. It may be better to store the current version.subversion string to /etc/sv/counterpartyd/release.txt (or wherever) and check for that.
That could also help us differ between update, rebuild and upgrade as well as automated updates (patches) and upgrades proposed here.