It would be helpful to include the hash of the most recent commit in both the client and server. That could help keep track of which code was last deployed to the server, as well as debugging issues caused by the browser cache not updating.
This wouldn't be too difficult, just find a couple of points in the client/server codebase where we should have the hash, add placeholders, then update the deploy.sh script to use sed to replace the placeholder with the actual commit hash.
It would be helpful to include the hash of the most recent commit in both the client and server. That could help keep track of which code was last deployed to the server, as well as debugging issues caused by the browser cache not updating.
This wouldn't be too difficult, just find a couple of points in the client/server codebase where we should have the hash, add placeholders, then update the deploy.sh script to use
sedto replace the placeholder with the actual commit hash.