Skip to content
This repository has been archived by the owner on Oct 5, 2020. It is now read-only.

Investigate replacing Roxy with ml-app-deployer CLI #548

Open
grtjn opened this issue Mar 1, 2018 · 0 comments
Open

Investigate replacing Roxy with ml-app-deployer CLI #548

grtjn opened this issue Mar 1, 2018 · 0 comments

Comments

@grtjn
Copy link
Contributor

grtjn commented Mar 1, 2018

Internal teams have shifted focus away from Roxy in favor of ml-gradle, and ml-app-deployer that is behind ml-gradle. Roxy is not using management rest api. We (the Roxy dev team) have long pondered moving over, but lingered too long to be able to make it happen. It kind of forces us now to move on, and migrate to something else. I managed to convince one of the core developers of ml-gradle to expose a CLI for ml-app-deployer, making it easier to use the core features of ml-gradle without needing Gradle itself. Lets investigate the impact..

@grtjn grtjn changed the title Investigate replace Roxy with ml-app-deployer CLI Investigate replacing Roxy with ml-app-deployer CLI Mar 1, 2018
gku11ava pushed a commit to gku11ava/slush-marklogic-node that referenced this issue Apr 6, 2018
…p-deployer CLI

Forked slush code to experiment with replacing Roxy with ml-app-deployer CLI.
- Converted ml-config.xml to ml-app-deployer/ml-gradle payloads in src/main/ml-config
- Moved REST extensions, library modules and transforms to src/main/ml-modules
- Removed Roxy folders/artifacts
- Updated slush and gulp init scripts to support gradle

Note: Had issues using property substitution with ml-app-deployer CLI so I'm
currently using ml-gradle.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant