Replies: 1 comment 1 reply
|
Hey, thanks for the feedback and sorry for the delay getting back to your question. It was set up to check Friday to Monday for any new sessions and automatically download to save time on pulling the data and computing when a user clicks into a session. I've now added an env variable where you can set what sessions you want to be auto downloaded and computed:
|
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
When I start up the container with the new single container architecture (which I love btw), I see in the container logs that it automatically started downloading FP1 and all the sessions within the current (Miami) race weekend. I don't recall this behaviour before v2.0, when I think it only started downloading data based on what I manually selected in the UI. I'd prefer that old behaviour as it can take a long time to get all the data for the entire weekend of activity. I tried deleting the entire app data folder to start from scratch but it didn't change the behaviour.
All reactions