Issue 29 - relax having a .couchapprc file

[ryanramage]

This will solve #29. @benoitc, can you have a quick review? This is my first erlang PR :)

[benoitc]

The reason a .couchapprc is(was?) needed is the same as in git it allows us to make sure we won't go in an infinite loop accros folders. Indeed it's used to send the couchapp from any folders inside just like git. ie if you are in _attachments/ you could sitill push the couchapp. Not sure it's a good change sinc eit remove some simplicity. What's your reasonning?

[ryanramage]

The patch still allows for detecting a .couchapprc file in a higher level
dir. This still works.

Most build tools expect to be run from the root dir, so I am not sure if
the feature of running in child dir is important.

My reasons:

• I want to reduce the amount of files a newbie has so see in a couchapp.
  It is distracting, And a couchapprc is in no way required to push.
• I also want to move to an attachment first style. I have code for this in
  my develop branch. This will allow for both styles of couchapp, the
  traditional, and webstyle. That way people can push a simple index.html in
  a folder if they want to. no other stuff.

On Wed, Oct 17, 2012 at 11:09 AM, Benoit Chesneau
[email protected]:

The reason a .couchapprc is(was?) needed is the same as in git it allows
us to make sure we won't go in an infinite loop accros folders. Indeed it's
used to send the couchapp from any folders inside just like git. ie if you
are in _attachments/ you could sitill push the couchapp. Not sure it's a
good change sinc eit remove some simplicity. What's your reasonning?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/31#issuecomment-9535316.