Thanks to a misunderstanding on my part around how external Docker volumes are named and configured, the current service isn't using an external volume for the database data. Given the transient nature of StatusPanel data, we're getting away with it, but it needs to be fixed as it fundamentaly affects data lifecycle expectations.
Thanks to a misunderstanding on my part around how external Docker volumes are named and configured, the current service isn't using an external volume for the database data. Given the transient nature of StatusPanel data, we're getting away with it, but it needs to be fixed as it fundamentaly affects data lifecycle expectations.