You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have two unused boolean fields in our storageadmin.Setup model that could serve us well as we move to a more multi-threaded arrangement such as is proposed in "Move to ASGI using Daphne #2941" & "Replace supervisord with further systemd intergration #2650"
It is proposed that we use these fields to indicate in-progress modifications to these major critical subsystems: enabling a shared overview mechanism where-by any associated changes can first check to ensure the relevant field is not False: indicating a setup/modification is in-progress. I.e. when-ever we are about to make such changes we can toggle the associated field to False, make the changes, then return to a True state upon the changes having been applied.
We have two unused boolean fields in our storageadmin.Setup model that could serve us well as we move to a more multi-threaded arrangement such as is proposed in "Move to ASGI using Daphne #2941" & "Replace supervisord with further systemd intergration #2650"
The existing used fields in this same model are:
It is proposed that we use these fields to indicate in-progress modifications to these major critical subsystems: enabling a shared overview mechanism where-by any associated changes can first check to ensure the relevant field is not False: indicating a setup/modification is in-progress. I.e. when-ever we are about to make such changes we can toggle the associated field to False, make the changes, then return to a True state upon the changes having been applied.
Linking to the associated setup stage indicated within our docs: https://rockstor.com/docs/installation/installer-howto.html#rockstor-setup-and-eula that uses the user & system flags within this model.
The text was updated successfully, but these errors were encountered: