Hi Pete, Thanks for the message. I am glad you are enjoying it so far :)
The *app* functionality came from a desire to separate the elements of design documents into a more structured approach and eventually came to include database documents (and attachments) as well; so in effect it can represent an entire *application*. Re-reading the man page I can see the documentation needs improving, I have raised #5 ( https://github.com/tmpfs/rlx/issues/5). Probably the easiest thing to do to get a grasp on it, is to browse the test fixture: https://github.com/tmpfs/rlx/tree/master/test/fixtures/app I will try to expand more on this with some updated documentation. You may also want to experiment with the *deploy* command as that follows all the recommended steps to re-deploy a view in a production environment. To get an idea of how the test fixture correlates to a single design document, with the rlx repository as the working directory, try this (couchdb running on localhost): ``` rlx i cd :lh db add mydb cd mydb app push test/fixtures/app -i myddoc app get myddoc ``` I just tried this with the 2.x alpha version and it is working fine, I see the entire collated design document in Fauxton. Hope that helps a little with the app command. Because the *app* command encapsulates a design document (and it's views) I hope this also answers the second part of your question. Although, executing and querying views still needs some work from what I recall to cater for pagination and large result sets. Feel free to raise questions and bugs on github! Cheers - muji. On 14 January 2016 at 09:59, Peter Figliozzi <[email protected]> wrote: > I have installed rlx and am keeping an interactive session open as I start > two new Couch projects this week. Lovely so far, especially the vim > integration. > > Muji, can you please explain the "app" functionality? Reading the man page > on "app", it feels like rlx is supposed to know about view, list, show, > etc., files in a project tree and put them into the design doc. And can > you give an example of creating a new design doc using the templates? I > get the same design doc created no matter what I put after "-t". > > Backing up a bit, maybe you could outline how rlx is intended to be used > with design docs and writing views, etc. > > Thanks much, > > Pete > > On Sun, Jan 10, 2016 at 10:40 PM, muji <[email protected]> wrote: > > > Hello, > > > > I am pleased to announce rlx[1], a full-featured command line interface > for > > couchdb: > > > > npm i -g rlx && rlx i > > > > Will launch an interactive session. Documentation is built in as man > pages > > with the `help` command - note that to edit documents `vim` is required. > > > > It was built and tested against couchdb 1.6.x and if people find it > useful > > I could contribute some more time for couchdb 2.x compatibility. > > > > All feedback very welcome - especially bugs[2]! > > > > Relax and enjoy! > > > > [1]: https://github.com/tmpfs/rlx > > [2]: https://github.com/tmpfs/rlx/issues > > >
