解释网站CouchDB的份量，是CouchDB的使用Apache捆绑不知何故，它是如何工作的？ [英] Explain CouchDB's serving of websites, is CouchDB bundled somehow with Apache and how does it work?
问题描述
我想了解如何CouchDB的工作。它是否配备了独立的Apache捆绑或是否在系统中使用Apache。我想了解它是如何决定在何处服务网站以及如何不同的方向进行。这是很重要的信息，因为我想了解如何实现Apache 2.2的mod代理 - 模的这里它的。我是否需要调整的CouchDB或者我需要调整一个单独的Apache进程？假设你有10 CouchDB的过程，要指导其结果站点A，你怎么能这样做呢？
对不起，我现在含糊，但我想了解如何不同的东西从一个网站到另一个组合，具有不同的授权，饼干等。我有一个问题，我的两个独立的网站你好.COM / myCouchDb / 和 hallo.de/someOthersite.html 分开工作。当我合并codeS，验证失败 - 我认为至少有三个不同的解决方案候选：
A）重定向从其他网站验证的东西到另一个（一个有点hackish）和/或
B）不知何故配置的Apache CouchDB的-settings，我曾尝试在蒲团但失败了。
C）的身份验证cookie存储一些目录或DB和刷新他们时，他们变老（或使用永不老饼干）
所以，我怎么能以不同的身份验证设置合并不同的CouchDB -instances在一起吗？假设你有10人，不同的身份验证Cookie，你想，让他们以某种方式纳入到同一个站点。你该怎么办呢？您调整网络-settings，阿帕奇-settings或CouchDB的-settings？或者你只是存储的cookie到某个目录或DB您刷新每次他们成为旧时代？
的 P.S。我是管理员，所以不要担心OAuth2.0的，我有认证饼干做任何我想用不同的实例。我只是不明白如何合并不同的实例。的
或许相关
<一个href=\"http://stackoverflow.com/questions/12397349/what-is-a-proxy-what-is-it-in-apache-does-it-have-many-different-meanings\">What是代理？这是什么在Apache的？它有许多不同的含义？
解决方案这听起来像你感到困惑的CouchDB的结构。 CouchDB是一个具有HTTP API本地JSON数据库。该API是通过受Mochiweb，就是里面的CouchDB捆绑一个Erlang基于网络服务器提供。只有一个CouchDB的服务器运行，但它运行的Erlang虚拟机（BEAM）内，有一个根本不同的架构，典型的Apache httpd的方法。
关于认证，拥有CouchDB的每个实例（服务器）_users包含密码和最小的帐户详细信息的数据库。作为管理员，你可以看到这个用被褥，虽然普通用户只能访问自己的个人资料。您可以将用户分配到不同的角色，然后将这些角色和用户到每个数据库。一旦_security对象被设置在一个数据块，则需要进行身份验证阅读，并且可以使用验证更新功能，以强制写入约束。一些简要信息<一个href=\"http://blog.couchbase.com/what%E2%80%99s-new-couchdb-10-%E2%80%94-part-4-security%E2%80%99n-stuff-users-authentication-authorisation-and-permissions\" rel=\"nofollow\">http://blog.couchbase.com/what%E2%80%99s-new-couchdb-10-%E2%80%94-part-4-security%E2%80%99n-stuff-users-authentication-authorisation-and-permissions和 http://blog.mattwoodward.com/2012/03/最终导至couchdb.html 以及wiki上。
I am trying to understand how CouchDB work. Does it come bundled up with separate Apache or does it use the Apache in the system. I am trying to understand how it determines where to serve the site and how are different directions done. This is important information because I am trying to understand how to implement the Apache 2.2 mod-proxy -module here with it. Do I need to tune CouchDB or do I need to tune a separate Apache process? Suppose you have 10 CouchDB processes and you want to direct their results to siteA, how can you do that?
Sorry I am now vague but I am trying to understand how to combine different things from one Site to another, having different authorization-cookies etc. I am having a problem where I have two separates sites
hello.com/myCouchDb/andhallo.de/someOthersite.htmlworking separately. When I merge the codes, the authentication fails -- I think there are at least three different solution candidates:A) redirect the verification things from the other site to another (a bit hackish) and/or
B) somehow configure the CouchDB Apache -settings, I have tried in Futon but failed.
C) store the authentication cookies to some dir or db and refresh them when they become old (or use never-old cookies)
So how can I merge different CouchDB -instances together with different authentication settings? Suppose you have ten people with different authentication cookies and you want to get them somehow incorporated to the same site. How can you do it? Do you tune network -settings, Apache -settings or CouchDB -settings? Or do you just stores the cookies to some directory or DB that you refresh every time they become old?
P.s. I am the admin so do not worry about the OAuth2.0, I have the authentication-cookies to do whatever I want with the different instances. I just cannot understand how to merge the different instances.
Perhaps related
解决方案It sounds like you're confused about the structure of CouchDB. CouchDB is a native JSON Database that has an HTTP API. That API is provided via Mochiweb, an Erlang based webserver that is bundled inside CouchDB. There's only one CouchDB server running, but it runs inside the Erlang Virtual Machine (BEAM) and has a fundamentally different architecture to the typical Apache httpd approach.
Regarding authentication, CouchDB has a per-instance (server) _users database that contains passwords and minimal account details. As an admin you can see this using Futon, although normal users only have access to their own profile. You can assign users into various roles, and then apply those roles and users to each database. Once the _security object is set on a DB, you need to be authenticated to read, and you can use validation update functions to enforce constraints on write. Some brief information on http://blog.couchbase.com/what%E2%80%99s-new-couchdb-10-%E2%80%94-part-4-security%E2%80%99n-stuff-users-authentication-authorisation-and-permissions and http://blog.mattwoodward.com/2012/03/definitive-guide-to-couchdb.html as well as on the wiki.
这篇关于解释网站CouchDB的份量，是CouchDB的使用Apache捆绑不知何故，它是如何工作的？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
