You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this would be fixed by forcing the application to restart again, after the entire deploy is complete. This would add to deploy restart time, but I think it would be worth it to enable users to see for themselves what version of the software is deployed and to be able to trust that the info is correct. There might also be other solutions I haven't thought of.
Version info in the footer of the application:
Tail of deploy@pdc-discovery-staging1:/opt/pdc_discovery/revisions.log:
The text was updated successfully, but these errors were encountered:
hectorcorrea
changed the title
Bug: When we deploy, the footer sometimes has state data
Bug: When we deploy, the footer sometimes has stale data
Nov 29, 2021
Problem: We are currently needing to deploy pdc_discovery twice in order to get the right info printed to the screen.
The version info on the screen gets read in via an initializer (https://github.com/pulibrary/pdc_discovery/blob/main/config/initializers/git_sha.rb). Because it is an initializer, it is only read one time, at application startup. The problem is that the application appears to be restarting before that file is completely written.
I believe this would be fixed by forcing the application to restart again, after the entire deploy is complete. This would add to deploy restart time, but I think it would be worth it to enable users to see for themselves what version of the software is deployed and to be able to trust that the info is correct. There might also be other solutions I haven't thought of.
Version info in the footer of the application:
Tail of
deploy@pdc-discovery-staging1:/opt/pdc_discovery/revisions.log
:The text was updated successfully, but these errors were encountered: