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
{{ message }}
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
Bootstrap won't notice if you remove an extra app server, database, role, user, or else from ml-config, and won't delete it for you. Current approach would be to wipe everything before removing it from ml-config, and bootstrap from a clean starting-point. It would be nice though if one could target one specific server or database with wipe to get it removed. Maybe something like:
./ml local wipe --servers=my-extra-server --databases=my-extra-database
It could potentially allow wiping items from MarkLogic that are not mentioned in ml-config (making it a very powerful tool to clean up a demo server), but that would be a bit sharp, and it should warn for that, and it should prevent wiping anything that is part of MarkLogic system (Security, Admin, App-services, ...)
The text was updated successfully, but these errors were encountered:
Bootstrap won't notice if you remove an extra app server, database, role, user, or else from ml-config, and won't delete it for you. Current approach would be to wipe everything before removing it from ml-config, and bootstrap from a clean starting-point. It would be nice though if one could target one specific server or database with wipe to get it removed. Maybe something like:
It could potentially allow wiping items from MarkLogic that are not mentioned in ml-config (making it a very powerful tool to clean up a demo server), but that would be a bit sharp, and it should warn for that, and it should prevent wiping anything that is part of MarkLogic system (Security, Admin, App-services, ...)
The text was updated successfully, but these errors were encountered: