I want to use the deploy tool to capture an existing configuration

[dmcassel]

Something like: "ml local capture", which would use the application name, servers, and ports, look at the target server, and build deploy/ml-config.xml. It would probably make sense for this to capture particular features (db settings, range indexes) rather than the whole config, so that the substitutions could remain in place.

[adamfowleruk]

I'll +1 this enhancement. I'm mainly bothered about Range Indexes, but CPF configuration and alert config would be good.

[peterskim12]

We should be able to leverage the out of the box packaging functionality for this, at least for the more recent MarkLogic versions.

[dmcassel]

Yeah, this feature will likely require ML6+, maybe ML7+.

[adamfowleruk]

Does this mean it won't get implemented, or will be delayed?

[dmcassel]

I expect it will get implemented. I can't promise when.

[mmalgeri]

+1 on this enhancement. The capture modules capability works fine. It would great to capture the content and any indexes created in either app builder or the admin interface

[grtjn]

+1 !!

[grtjn]

I suggest taking a particular app-server as starting point, and pull details from anything it points to or uses. Maybe have a 'wizard' ask what to include or not..

[grtjn]

I improved support for capturing ml-config. The new parameter --ml-config accepts comma-separated lists of dbs, forests, servers, and mimes using --databases= --forests= --servers= --mimes= to capture specific parts of the full ml-config. Leaving them out will default to those for the current project.

Support for users and roles takes a little more effort unfortunately..

Still an 'undocumented' feature. Not mature enough to add to Help just yet..

[grtjn]

I think this progressed sufficiently to mark this as closed. Agree?

[dmcassel]

I concur. If there are enhancements to be done to the existing functionality, those can be added as new issues.