Now that the pipeline is back up and running, we are going to update the heck out of the summary and analysis code, as right now, the website only has a crude time series figure, and there's clearly much we can do!
π§΅ / fin
https://t.co/mOvtrYL0b3 is back to daily automatic updates of salvage data! π§π
The stack ran hands-off every ding dong day from 2020-01-30 to 2021-06-11 when @travisci stopped free runs οΏ½οΏ½π
Been busy and sans π² support, but finally migrated to @GitHubActions! ππΌ
π§΅ 1/
The shift from @travisci to @github runners was not too horrible, all things considered, just needed some time to work out the kinks.
The old travis file is still in the repo for comparison to the github workflow, and its really similar.
https://t.co/1nFqy8kgfv
@NelsonStauffer you're welcome!
let me know if you have any ?s (feel free to email, obvi)
it's also been a minute since i wrote that all up, so let me know if there's new and cool stuff!
@NelsonStauffer i definitely was having major issues with the downloading stuff that got smoothed out when i shifted to using wget
there's some weird things about the timeouts and such that can trip things, not sure if that's related to your issues, but maybe?
@NelsonStauffer ok!
so, i have a setup that does something like this, but not directly like you have it here
it uses a two-image approach
https://t.co/30h5h77Eyr explains the dirty details on the container that gets the data
https://t.co/vM0qTCMGo2 explains how i use it