You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by mar-ia <gi...@git.apache.org> on 2015/04/12 17:20:12 UTC
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
GitHub user mar-ia opened a pull request:
https://github.com/apache/couchdb-documentation/pull/19
A base to build on for 2.0
This is basically my couchdb-crazy rep, converted and modified.
The documentation is not done with this, but it is a base to build on.
This is all I have on 2.0, so if anyone wants to fork this branch and continue building on it before merging, please do so :)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mar-ia/couchdb-documentation cluster
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-documentation/pull/19.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #19
----
commit 856ca85ae8c45c73533fc863ae66dcf21a6f74bd
Author: Maria Andersson <ma...@dualpose.com>
Date: 2015-04-13T14:47:01Z
A base to build on for 2.0
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by kxepal <gi...@git.apache.org>.
Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92850783
Thank you! (:
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by kxepal <gi...@git.apache.org>.
Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92764010
@janl why not to fix them before? since they are pretty trivial.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by kxepal <gi...@git.apache.org>.
Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92084051
That's great contribution! Again (:
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/couchdb-documentation/pull/19
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by mar-ia <gi...@git.apache.org>.
Github user mar-ia commented on the pull request:
https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92767820
And already fixed :)
I did some more fixes and some rewrites too, in a try to make things more clear.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by kxepal <gi...@git.apache.org>.
Github user kxepal commented on a diff in the pull request:
https://github.com/apache/couchdb-documentation/pull/19#discussion_r28204714
--- Diff: src/cluster/sharding.rst ---
@@ -0,0 +1,289 @@
+.. Licensed under the Apache License, Version 2.0 (the "License"); you may not
+.. use this file except in compliance with the License. You may obtain a copy of
+.. the License at
+..
+.. http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+.. WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+.. License for the specific language governing permissions and limitations under
+.. the License.
+
+.. _cluster/sharding:
+
+========
+Sharding
+========
+
+.. _cluster/sharding/scaling-out:
+
+Scaling out
+===========
+
+Normally you start small and grow over time. In the beginning you might do just
+fine with one node, but as your data and number of clients grows, you need to
+scale out.
+
+For simplicity we will start fresh and small.
+
+Start node1 and add a database to it. To keep it simple we will have 2 shards
+and no replicas.
+
+.. code-block:: bash
+
+ curl -X PUT "http://xxx.xxx.xxx.xxx:5984/small?n=1&q=2" --user daboss
+
+If you look in the directory ``data/shards`` you will find the 2 shards.
+
+.. code-block:: text
+
+ data
--- End diff --
How about to explicitly how here that data, shards and others are directories? Like:
```
data/
+-- shards/
+-- 00000000-7fffffff/
| +-- small.1425202577.couch
+-- 80000000-ffffffff/
+-- small.1425202577.couch
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by kxepal <gi...@git.apache.org>.
Github user kxepal commented on a diff in the pull request:
https://github.com/apache/couchdb-documentation/pull/19#discussion_r28236027
--- Diff: src/cluster/sharding.rst ---
@@ -0,0 +1,289 @@
+.. Licensed under the Apache License, Version 2.0 (the "License"); you may not
+.. use this file except in compliance with the License. You may obtain a copy of
+.. the License at
+..
+.. http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+.. WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+.. License for the specific language governing permissions and limitations under
+.. the License.
+
+.. _cluster/sharding:
+
+========
+Sharding
+========
+
+.. _cluster/sharding/scaling-out:
+
+Scaling out
+===========
+
+Normally you start small and grow over time. In the beginning you might do just
+fine with one node, but as your data and number of clients grows, you need to
+scale out.
+
+For simplicity we will start fresh and small.
+
+Start node1 and add a database to it. To keep it simple we will have 2 shards
+and no replicas.
+
+.. code-block:: bash
+
+ curl -X PUT "http://xxx.xxx.xxx.xxx:5984/small?n=1&q=2" --user daboss
+
+If you look in the directory ``data/shards`` you will find the 2 shards.
+
+.. code-block:: text
+
+ data
+ shards
+ 00000000-7fffffff
+ small.1425202577.couch
+ 80000000-ffffffff
+ small.1425202577.couch
+
+Now, go to the admin panel
+
+.. code-block:: text
+
+ http://xxx.xxx.xxx.xxx:5986/_utils
+
+and look in the database ``_dbs``, it is here that the metadata for each
+database is stored. As the database is called small, there is a document called
+small there. Let us look in it. Yes, you can get it with curl too:
+
+.. code-block:: javascript
+
+ curl -X GET "http://xxx.xxx.xxx.xxx:5986/_dbs/small"
+
+ {
+ "_id": "small",
+ "_rev": "1-5e2d10c29c70d3869fb7a1fd3a827a64",
+ "shard_suffix": [
+ 46,
+ 49,
+ 52,
+ 50,
+ 53,
+ 50,
+ 48,
+ 50,
+ 53,
+ 55,
+ 55
+ ],
+ "changelog": [
+ [
+ "add",
+ "00000000-7fffffff",
+ "node1@xxx.xxx.xxx.xxx"
+ ],
+ [
+ "add",
+ "80000000-ffffffff",
+ "node1@xxx.xxx.xxx.xxx"
+ ]
+ ],
+ "by_node": {
+ "node1@xxx.xxx.xxx.xxx": [
+ "00000000-7fffffff",
+ "80000000-ffffffff"
+ ]
+ },
+ "by_range": {
+ "00000000-7fffffff": [
+ "node1@xxx.xxx.xxx.xxx"
+ ],
+ "80000000-ffffffff": [
+ "node1@xxx.xxx.xxx.xxx"
+ ]
+ }
+ }
+
+* ``_id`` The name of the database.
+* ``_rev`` The current revision of the metadata.
+* ``shard_suffix`` The numbers after small and before .couch. The number of
+ seconds after UNIX epoch that the database was created. Stored in ASCII.
+* ``changelog`` Self explaining. Only for admins to read.
+* ``by_node`` Which shards each node have.
+* ``by_rage`` On which nodes each shard is.
+
+Nothing here, nothing there, a shard in my sleeve
+-------------------------------------------------
+
+Start node2 and add it to the cluster. Check in ``/_membership`` that the
+nodes are talking with each other.
+
+If you look in the directory ``data`` on node2, you will see that there is no
+directory called shards.
+
+Go to Fauxton and edit the metadata for small, so it looks like this:
+
+.. code-block:: javascript
+
+ {
+ "_id": "small",
+ "_rev": "1-5e2d10c29c70d3869fb7a1fd3a827a64",
+ "shard_suffix": [
+ 46,
+ 49,
+ 52,
+ 50,
+ 53,
+ 50,
+ 48,
+ 50,
+ 53,
+ 55,
+ 55
+ ],
+ "changelog": [
+ [
+ "add",
+ "00000000-7fffffff",
+ "node1@xxx.xxx.xxx.xxx"
+ ],
+ [
+ "add",
+ "80000000-ffffffff",
+ "node1@xxx.xxx.xxx.xxx"
+ ],
+ [
+ "add",
+ "00000000-7fffffff",
+ "node2@yyy.yyy.yyy.yyy"
+ ],
+ [
+ "add",
+ "80000000-ffffffff",
+ "node2@yyy.yyy.yyy.yyy"
+ ]
+ ],
+ "by_node": {
+ "node1@xxx.xxx.xxx.xxx": [
+ "00000000-7fffffff",
+ "80000000-ffffffff"
+ ],
+ "node2@yyy.yyy.yyy.yyy": [
+ "00000000-7fffffff",
+ "80000000-ffffffff"
+ ]
+ },
+ "by_range": {
+ "00000000-7fffffff": [
+ "node1@xxx.xxx.xxx.xxx",
+ "node2@yyy.yyy.yyy.yyy"
+ ],
+ "80000000-ffffffff": [
+ "node1@xxx.xxx.xxx.xxx",
+ "node2@yyy.yyy.yyy.yyy"
+ ]
+ }
+ }
+
+Then press Save and marvel at the magic. The shards are now on node2 too! We
+now have ``n=2``!
+
+If the shards are large, then you can copy them over manually and only have
+CouchDB syncing the changes from the last minutes instead.
+
+.. _cluster/sharding/move:
+
+Moving Shards
+=============
+
+When you get to ``n=3`` you should start moving the shards instead of adding
+more replicas.
+
+.. warning::
+ If you have ``n<2`` then you have to stop all writes to the database or you
+ will *LOSE DATA*!
--- End diff --
Really loose?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by kxepal <gi...@git.apache.org>.
Github user kxepal commented on a diff in the pull request:
https://github.com/apache/couchdb-documentation/pull/19#discussion_r28235870
--- Diff: src/cluster/setup.rst ---
@@ -0,0 +1,160 @@
+.. Licensed under the Apache License, Version 2.0 (the "License"); you may not
+.. use this file except in compliance with the License. You may obtain a copy of
+.. the License at
+..
+.. http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+.. WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+.. License for the specific language governing permissions and limitations under
+.. the License.
+
+.. _cluster/setup:
+
+=====
+Setup
+=====
+
+Everything you need to know to prepare the cluster for the installation of
+CouchDB.
+
+Firewall
+========
+
+If you do not have a firewall between your servers, then you can skip this.
+
+CouchDB in cluster mode uses the port ``5984`` just as standalone, but is also
+uses ``5986`` for the admin interface.
+
+Erlang uses TCP port ``4369`` (EPMD) to find other nodes, so all servers must be
+able to speak to each other on this port. In an Erlang Cluster, all nodes are
+connected to all other nodes. A mesh.
+
+.. warning::
+ Do not open up this port, ``4369`` to the Internet, or any other
+ untrusted network. Failing to close this port will leave you wide open!
--- End diff --
Good recommendation. However, you're not very wide opened since cookie is required to make a connection.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by sebastianrothbucher <gi...@git.apache.org>.
Github user sebastianrothbucher commented on a diff in the pull request:
https://github.com/apache/couchdb-documentation/pull/19#discussion_r28206325
--- Diff: src/cluster/nodes.rst ---
@@ -0,0 +1,65 @@
+.. Licensed under the Apache License, Version 2.0 (the "License"); you may not
+.. use this file except in compliance with the License. You may obtain a copy of
+.. the License at
+..
+.. http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+.. WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+.. License for the specific language governing permissions and limitations under
+.. the License.
+
+.. _cluster/nodes:
+
+===============
+Node Management
+===============
+
+.. _cluster/nodes/add:
+
+Adding a node
+=============
+
+Go to ``http://server1:45984/_membership`` to see the name of the node and all
+the nodes it knows about and are connected too.
+
+.. code-block:: text
+
+ curl -X PUT "http://xxx.xxx.xxx.xxx:5984/_membership" --user admin-user
--- End diff --
didn't try now - but is it PUT or GET?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by janl <gi...@git.apache.org>.
Github user janl commented on the pull request:
https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92763742
Great work @mar-ia! Let’s get this merged and file issues for the line-comments to fix soon after.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by kxepal <gi...@git.apache.org>.
Github user kxepal commented on a diff in the pull request:
https://github.com/apache/couchdb-documentation/pull/19#discussion_r28235714
--- Diff: src/cluster/nodes.rst ---
@@ -0,0 +1,65 @@
+.. Licensed under the Apache License, Version 2.0 (the "License"); you may not
+.. use this file except in compliance with the License. You may obtain a copy of
+.. the License at
+..
+.. http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+.. WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+.. License for the specific language governing permissions and limitations under
+.. the License.
+
+.. _cluster/nodes:
+
+===============
+Node Management
+===============
+
+.. _cluster/nodes/add:
+
+Adding a node
+=============
+
+Go to ``http://server1:45984/_membership`` to see the name of the node and all
+the nodes it knows about and are connected too.
+
+.. code-block:: text
+
+ curl -X PUT "http://xxx.xxx.xxx.xxx:5984/_membership" --user admin-user
--- End diff --
Indeed, `/_membership` [accepts only `GET`](https://github.com/apache/couchdb-mem3/blob/master/src/mem3_httpd.erl#L22-L29)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by kxepal <gi...@git.apache.org>.
Github user kxepal commented on a diff in the pull request:
https://github.com/apache/couchdb-documentation/pull/19#discussion_r28235615
--- Diff: src/cluster/nodes.rst ---
@@ -0,0 +1,65 @@
+.. Licensed under the Apache License, Version 2.0 (the "License"); you may not
+.. use this file except in compliance with the License. You may obtain a copy of
+.. the License at
+..
+.. http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+.. WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+.. License for the specific language governing permissions and limitations under
+.. the License.
+
+.. _cluster/nodes:
+
+===============
+Node Management
+===============
+
+.. _cluster/nodes/add:
+
+Adding a node
+=============
+
+Go to ``http://server1:45984/_membership`` to see the name of the node and all
+the nodes it knows about and are connected too.
+
+.. code-block:: text
+
+ curl -X PUT "http://xxx.xxx.xxx.xxx:5984/_membership" --user admin-user
+
+ {"all_nodes":["node1@xxx.xxx.xxx.xxx"],"cluster_nodes":["node11@xxx.xxx.xxx.xxx"]}
+
+* ``all_nodes`` are all the nodes thats this node knows about.
+* ``cluster_nodes`` are the nodes that are connected to this node.
+
+To add a node simply do:
+
+.. code-block:: text
+
+ curl -X PUT "http://xxx.xxx.xxx.xxx:5986/_nodes/node2@yyy.yyy.yyy.yyy" -d {}
+
+Now look at ``http://server1:5984/_membership`` again.
+
+.. code-block:: text
+
+ {"all_nodes":["minion1@xxx.xxx.xxx.xxx","minion2@yyy.yyy.yyy.yyy"],"cluster_nodes":["minion1@xxx.xxx.xxx.xxx","minion2@yyy.yyy.yyy.yyy"]}
--- End diff --
This example could be pretty printed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by kxepal <gi...@git.apache.org>.
Github user kxepal commented on a diff in the pull request:
https://github.com/apache/couchdb-documentation/pull/19#discussion_r28204718
--- Diff: src/cluster/sharding.rst ---
@@ -0,0 +1,289 @@
+.. Licensed under the Apache License, Version 2.0 (the "License"); you may not
+.. use this file except in compliance with the License. You may obtain a copy of
+.. the License at
+..
+.. http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
+.. WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+.. License for the specific language governing permissions and limitations under
+.. the License.
+
+.. _cluster/sharding:
+
+========
+Sharding
+========
+
+.. _cluster/sharding/scaling-out:
+
+Scaling out
+===========
+
+Normally you start small and grow over time. In the beginning you might do just
+fine with one node, but as your data and number of clients grows, you need to
+scale out.
+
+For simplicity we will start fresh and small.
+
+Start node1 and add a database to it. To keep it simple we will have 2 shards
+and no replicas.
+
+.. code-block:: bash
+
+ curl -X PUT "http://xxx.xxx.xxx.xxx:5984/small?n=1&q=2" --user daboss
+
+If you look in the directory ``data/shards`` you will find the 2 shards.
+
+.. code-block:: text
+
+ data
+ shards
+ 00000000-7fffffff
+ small.1425202577.couch
+ 80000000-ffffffff
+ small.1425202577.couch
+
+Now, go to the admin panel
+
+.. code-block:: text
+
+ http://xxx.xxx.xxx.xxx:5986/_utils
+
+and look in the database ``_dbs``, it is here that the metadata for each
+database is stored. As the database is called small, there is a document called
+small there. Let us look in it. Yes, you can get it with curl too:
+
+.. code-block:: javascript
+
+ curl -X GET "http://xxx.xxx.xxx.xxx:5986/_dbs/small"
+
+ {
+ "_id": "small",
+ "_rev": "1-5e2d10c29c70d3869fb7a1fd3a827a64",
+ "shard_suffix": [
+ 46,
+ 49,
+ 52,
+ 50,
+ 53,
+ 50,
+ 48,
+ 50,
+ 53,
+ 55,
+ 55
+ ],
--- End diff --
bad align
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by sebastianrothbucher <gi...@git.apache.org>.
Github user sebastianrothbucher commented on the pull request:
https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92104794
this is just GREAT - definitely +1 on merging it in
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by janl <gi...@git.apache.org>.
Github user janl commented on the pull request:
https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92795169
@kxepal all I meant: I don’t think these are blockers. We can always fix them before, too. Sorry for being unclear :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by kxepal <gi...@git.apache.org>.
Github user kxepal commented on the pull request:
https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92777684
@mar-ia great! Could you only squash your commits please. If you think it's ready, I'll merge it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-documentation pull request: A base to build on for 2.0
Posted by mar-ia <gi...@git.apache.org>.
Github user mar-ia commented on the pull request:
https://github.com/apache/couchdb-documentation/pull/19#issuecomment-92842306
Squashed.
@kxepal Please do :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---