-
Notifications
You must be signed in to change notification settings - Fork 66
RFE: skip XDBC server on ML8 #373
Comments
+1 on those being defaults |
Can mlcp specify a different database yet? That was a factor previously that caused me to have to keep installing new XCC instances against my will. I feel like I saw that it could in the latest version. |
Yes, as of MarkLogic 8 / MLCP 1.3-1. http://docs.marklogic.com/guide/relnotes/chap3#id_46078 |
Then +1 for me too. |
And if i read correctly, it is against the app specific rest api anyhow. I'd look forward to it! |
Fix #396 first.. |
@paxtonhare / @dmcassel: Wondering, would that work for hybrid apps as well, or rest only? By the way, we could make bootstrap and mlcp check properties against server-version, and have it suggest changing settings to save an app-server. Nice touch for existing projects.. |
@grtjn should work fine for hybrid/mvc/bare -- the point is having an XDBC server and the ability to specify where it's loading content. Port 8000 provides that in ML8. |
I was just wondering whether the url-rewriter was influencing that, but totally forgot about port 8000.. :) |
Depends on #396, postponing it for now.. |
In retrospect I'm wondering why the database option of MLCP is keeping us back here. We don't use that option now, and can run MLCP happily against app-port since ML8. I'm using that all the time. Actually, we already enforce In short, I see no dependency on #396 (which I think is obsolete too since ML8), particularly if MLCP will just run against app-port, which would be the case with above settings. Makes sense? |
ML8 REST API instances support XCC requests, and do not require a separate XDBC server. Roxy supports this now, by setting
install-xcc=false
andxcc-port=${app-port}
indeploy/build.properties
prior to bootstrapping. Can we make these settings the defaults for ML 8 REST/hybrid environments?The text was updated successfully, but these errors were encountered: