בעיה בבנייה מחדש בגלל כיבוי איטי של מסד הנתונים

Thanks-- so ./launcher rebuild web_only (or rebuild data) instead of ./launcher rebuild app, and I’d need to closely read updates to see when postgres or redis is updated to manually update them as well. And the main advantage over standalone is rebuilds don’t need to wait for the database to shutdown and then start back up, rolling-back transactions if it was killed.

But with Falco’s latest changes, the DB should never be killed unless it takes >10min to shutdown, which it certainly won’t unless we get a metric f-ton more users. So the updates won’t fail due to that problem, and the main impact is just to make updates take a couple minutes longer.

My read is that ultimately the change adds a bunch of complexity and mental overhead for really very little gain. Please correct me if I’m wrong, that isn’t meant to be sarcastic/etc.

Just as a bit of background, the change would have to offer substantial benefits to be worth that overhead because this is all an unpaid favor by me (one now stretching out 15 years+, but nonetheless), not my job. Real YMMV situation there.