Juan Pablo Tosca Villanueva (Sep 14 2023 at 19:10): Juan Pablo Tosca Villanueva (Sep 14 2023 at 19:10):Just out of curiosity, when do you normally publish the recordings on the website @Philip Durbin ?
I am watching the recordings of some of the previous weeks, and I was thinking about the #9886 issue mentioned on last week meeting about the timer on configbaker, probably I am overthinking this since you can manually start this container at a later point individually if the timer takes longer, but probably beside just expiring the timer could be on a loop with a timer in between? Probably like if it didn't receive a response after 1m then it would take a break let's say 1 minute and then try again? I just wanted to bring the idea up just in case that would be something of interest to explore in case someone is trying to develop in a slower environment.
Philip Durbin 🚀 (Sep 14 2023 at 20:06):@Juan Pablo Tosca Villanueva sorry, busy day, I just added the recording to https://ct.gdcc.io so please refresh.
Philip Durbin 🚀 (Sep 14 2023 at 20:08):So, configbaker is already on a loop. It used to loop for 2 minutes by default. Once we merge that PR, it will change to 3. (@Oliver Bertuch or @Don Sizemore please feel free to approve that PR, if you are so inclined!)
Philip Durbin 🚀 (Sep 14 2023 at 20:09):As for running configbaker (again?) later, I haven't tried it. You're welcome to try. :big_smile:
Philip Durbin 🚀 (Sep 14 2023 at 20:09):Before configbaker we just had some scripts to run afterward. Let me show you.
Philip Durbin 🚀 (Sep 14 2023 at 20:10):Oh. I guess that was mid-release.
Philip Durbin 🚀 (Sep 14 2023 at 20:12): Philip Durbin 🚀 (Sep 14 2023 at 20:12):Where we had a script called docker-final-setup.sh.
Juan Pablo Tosca Villanueva (Sep 14 2023 at 23:55):Philip Durbin said:
Juan Pablo Tosca Villanueva sorry, busy day, I just added the recording to https://ct.gdcc.io so please refresh.
Thanks that is great!
Philip Durbin 🚀 (Sep 14 2023 at 23:56):Sure, no problem.
Last updated: Oct 30 2025 at 05:14 UTC