This appears to work. In order to trigger the update on deploy, bitcoind must be deleted. Also, it seems like running bitcoind --version now creates a settings.json file, which will have the wrong permissions since it's run as root, so we chown it to the right user.
This appears to work. In order to trigger the update on deploy, bitcoind must be deleted. Also, it seems like running
bitcoind --versionnow creates asettings.jsonfile, which will have the wrong permissions since it's run as root, so we chown it to the right user.