Thank you, Dave! Of course Roxy supports multiple environments. I think the main differences are:
- the use of a JSON format to organize the environment configuration, supporting (eventually) all properties from the Management API; - the ability to have any arbitrary import graph between the environment files, so anyone can create a new environment by importing (inheriting from) any existing environment (or several of them), or even by overriding some values from the command line, and without having to change build.properties See examples of such files at https://github.com/fgeorges/mlproj/tree/master/test/environs. The goal is not really to compete with Roxy (yet :-p), but rather to try and see where we can go with an alternative that does not have to guarantee backward compatibility. Regards, -- Florent Georges H2O Consulting http://h2o.consulting/ On 29 March 2017 at 05:01, Dave Cassel wrote: > A couple notes: > > - the Roxy Deployer does support multiple environments ( > https://github.com/marklogic/roxy/wiki/Environment-properties > <https://github.com/marklogic/roxy/wiki/Environment-properties>); > could you say more about the flexibility? > - agreed that more people know JavaScript than Ruby > - the Roxy Deployer supports app-types MVC, REST, and bare (the source > code is whatever you choose to provide), with scaffolding available for MVC > (controllers & views) and REST (extensions & transforms) > > In case this comes across as critical: while I'm a fan of focusing effort > on a small number projects, if there's demand for a different approach then > I support it. My "Community Manager" hat takes precedence over my "Roxy > Maintainer" hat. :) I've seen growing support for ml-gradle, based largely > on its use of the Management API, and I think it's a great tool. > > -- > Dave Cassel, @dmcassel <https://twitter.com/dmcassel> > Technical Community Manager > MarkLogic Corporation <http://www.marklogic.com/> > http://developer.marklogic.com/ > > > From: <general-boun...@developer.marklogic.com> on behalf of Florent > Georges <li...@fgeorges.org> > Reply-To: MarkLogic Developer Discussion <general@developer.marklogic.com> > Date: Tuesday, March 28, 2017 at 11:45 AM > To: MarkLogic Developer Discussion <general@developer.marklogic.com> > Subject: Re: [MarkLogic Dev General] mlproj, yet another project manager > for MarkLogic > > Hi Andreas, > > Thank you! Yes, it covers essentially the same function. It is still in > development, and a bit experimental. So far, the main difference is the > environment file format, that is more flexible to describe MarkLogic > environments <http://mlproj.org/environments>. > > It is also meant to be extensible, and because it uses JavaScript, I hope > it will be easier for people to extend it than using Ruby (just because it > is better well-known). > > Another aspect is that is it meant to support several kinds of projects (a > web application serving web pages in MarkLogic, or providing a RESTful API, > etc.) The goal is to support people to create new types of projects, so > users can start with a full-fledged scaffolding for the type of application > then want to create (and not be restricted to only these I can come up > with.) > > But as I said, it is still experimental, so I hope it will take feedback > into account, especially features that newcomers and day-to-day users think > are important. > > Regards, > > -- > Florent Georges > H2O Consulting > http://h2o.consulting/ > > > On 28 March 2017 at 16:49, Andreas Hubmer wrote: > >> Hi Florent, >> >> Sounds interesting. >> >> From what I've seen so far mlproj is similar to Roxy. >> Can you describe the differences? >> >> Regards, >> Andreas >> >> >> 2017-03-28 16:13 GMT+02:00 Florent Georges <li...@fgeorges.org>: >> >>> Hi Dave, >>> >>> I do not know mlsound, so I can't really say. But given your question, >>> the main difference is probably that mlproj is not for the Node.js >>> environment. It only requires it as an >>> "implementation detail", but it really is for MarkLogic, for any >>> MarkLogic project, regardless of the technology it uses (JavaScript, >>> XQuery, triples...) It only addresses the server-side of projects, nothing >>> about any other layer, like Node.js. >>> >>> I am not sure about your second question. But if the question is "are >>> the environment described using the same payload one can send to the Mgmt >>> API to create databases and servers?", then the answer is no. I think it >>> is an important feature of mlproj, that environments are described in a >>> specific format, aimed at being clearer and more maintainable than the API >>> payloads. Look at http://mlproj.org/environments (and the examples >>> mentioned in the first paragraph.) >>> >>> Thank you for your interest :-) Regards, >>> >>> -- >>> Florent Georges >>> H2O Consulting >>> http://h2o.consulting/ >>> >>> >>> On 27 March 2017 at 18:40, Dave Cassel wrote: >>> >>>> Hi Florent, >>>> >>>> Could you comment on how mlproj is different from mlsound, which is >>>> also a Management API-based deployment tool for the Node.js environment? >>>> >>>> Do you use Management API payloads for your on-disk structure? >>>> >>>> Dave. >>>> >>>> -- >>>> Dave Cassel, @dmcassel <https://twitter.com/dmcassel> >>>> Technical Community Manager >>>> MarkLogic Corporation <http://www.marklogic.com/> >>>> http://developer.marklogic.com/ >>>> >>>> >>>> From: <general-boun...@developer.marklogic.com> on behalf of Florent >>>> Georges <li...@fgeorges.org> >>>> Reply-To: MarkLogic Developer Discussion <general@developer.marklogic.c >>>> om> >>>> Date: Monday, March 27, 2017 at 7:27 AM >>>> To: MarkLogic Developer Discussion <general@developer.marklogic.com> >>>> Subject: [MarkLogic Dev General] mlproj, yet another project manager >>>> for MarkLogic >>>> >>>> Hi, >>>> >>>> I am happy to announce *mlproj*, yet another project manager for >>>> MarkLogic: >>>> >>>> http://mlproj.org/ >>>> >>>> Thanks to Node and NPM, it is dead easy to install and extend. It >>>> comes with a simple JSON format to describe MarkLogic environments, and >>>> commands to create and deploy them. Though of course it is not restricted >>>> to JavaScript and JSON, and handles XML and XQuery, and triples and SPARQL >>>> all the same. >>>> >>>> It is still in development, and is expected to evolve quite rapidly. >>>> But it is already usable for most simple actions. >>>> >>>> Any feedback welcome, either here, or on http://twitter.com/fgeorges, >>>> or on http://github.com/fgeorges/mlproj. >>>> >>>> Have fun! >>>> >>>> Regards, >>>> >>>> -- >>>> Florent Georges >>>> H2O Consulting >>>> http://h2o.consulting/ >>>> >>>> >>>> >>> >> _______________________________________________ >> General mailing list >> General@developer.marklogic.com >> Manage your subscription at: >> http://developer.marklogic.com/mailman/listinfo/general >> >> > > > > > _______________________________________________ > General mailing list > General@developer.marklogic.com > Manage your subscription at: > http://developer.marklogic.com/mailman/listinfo/general > >
_______________________________________________ General mailing list General@developer.marklogic.com Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
