couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michelle Phung <>
Subject Re: Project Fauxton Feedback
Date Thu, 17 Sep 2015 16:26:37 GMT
Hi Eli,

We don’t use a schedule for the NPM package or Fauxton releases. The reason being is because
we enjoy being able to fix bugs and merge them, and have that code be the latest code everyone
works off of. The master branch moves FAST, from my point of view.  Fauxton comes standard
shipped with CouchDB, and that is considered the latest stable tested release.  The NPM Fauxton
package is a fairly new development for us, but auxiliary to all the other things we have
to do :)

Unfortunately, the npm package fauxton@1.0.3 is a bit outdated (4 months), and we haven’t
integrated a work flow that updates it every time we commit a fix, but I will bring that up
moving forward for us.

I am going to bug Robert K. to show me how to update the node package tomorrow, and so it
should be updated soon! hopefully it’ll be available over the weekend/next week for you

Try the github repo in the meantime though!


> On Sep 16, 2015, at 8:32 PM, Eli Stevens (Gmail) <> wrote:
> I just (mostly) followed the instructions at (except for the -g part,
> since I didn't want it global):
> And ran the following:
> npm install fauxton
> cd node_modules/fauxton/node_modules/.bin/ ; ./grunt couchapp_deploy
> Which had references to "fauxton@1.0.3 node_modules/fauxton" in the output.
> Does that answer the question?
> Aside, is what I did the best way to get a mostly-stable version of
> fauxton? I assumed that would be more stable that pulling directly
> from git. This goes back to my earlier question about releases; it's
> not clear what the best way to get something new and usable is.
> Thanks,
> Eli
> On Wed, Sep 16, 2015 at 3:06 PM, Michelle Phung <> wrote:
>> Hi Eli,
>> JIRA is the place for bugs.
>> Its kind of tough to get people to look at it though, since there’s a lot going
on with JIRA, and its a little endless.
>> I thought we fixed the problem you described though.
>> Did you pull from, the master branch?
>> Michelle
>>> On Sep 16, 2015, at 5:50 PM, Eli Stevens (Gmail) <>
>>> Where is the appropriate place to file bugs against Fuaxton? Most
>>> recent I see in JIRA is Feb. 15th of this year.
>>> As of a couple of hours ago when I updated my install, the view query
>>> options UI wasn't respecting start and end keys (though the link to
>>> the raw JSON is correct).
>>> On Wed, Aug 19, 2015 at 11:34 AM, Eli Stevens (Gmail)
>>> <> wrote:
>>>> I agree with kexpal's comment on the PR; large documents would make
>>>> this very, very painful.
>>>> I was asking for a view checkbox that would result in a 3rd column for
>>>> view results (key / value / optional doc) that defaulted to off, so
>>>> that I could include it when appropriate.
>>>> Cheers,
>>>> Eli
>>>> On Wed, Aug 19, 2015 at 8:26 AM, Robert Kowalski <>
>>>>> Thank you for your feedback!
>>>>> Based on the feedback we will try to enable `include_docs` per default:
>>>>> What do you think?
>>>>> On Wed, Aug 19, 2015 at 9:55 AM, James Dingwall
>>>>> <> wrote:
>>>>>> Eli Stevens (Gmail) wrote:
>>>>>>> On Tue, Aug 18, 2015 at 1:11 AM, James Dingwall
>>>>>>> <> wrote:
>>>>>>>> I get the impression that more whizzy effects (fade in/out,
sliding divs
>>>>>>>> etc) have been added which don't play nicely with remote
sessions with
>>>>>>>> low bandwidth so a preference to use more basic transitions
would be
>>>>>>>> useful.
>>>>>>> +1
>>>>>>> Note that it looks like the mailing list strips screenshots,
so you
>>>>>>> might need to host-and-link them.
>>>>>> Thanks Eli, I didn't notice that when I received a copy of my post.
>>>>>> have placed my unchanged comments and screen shots in a github gist
>>>>>> available from:
>>>>>> James
>>>>>> Zynstra is a private limited company registered in England and Wales
>>>>>> (registered number 07864369). Our registered office and Headquarters
are at
>>>>>> The Innovation Centre, Broad Quay, Bath, BA1 1UD. This email, its
>>>>>> and any attachments are confidential. If you have received this message
>>>>>> error please delete it from your system and advise the sender immediately.

View raw message