The Official Couchbase .NET SDK
Chat with us on Discord | Couchbase Forums
- master is 3.9 development branch
- release27 is 2.7.X development branch
- release13 is 1.3.X development branch
To get up and running with the SDK, please visit the online documentation.
We maintain a collection of both unit and integration test projects.
Couchbase.UnitTests contains environment independent tests and do not require a local cluster to run.
Couchbase.IntegrationTests contains tests that are run against a real Couchbase Server and has different requirements depending on what server version you are running them against:
Couchbase Server 4.0+
- The "beer-sample" and "travel-sample" sample buckets installed. They can be installed by logging into the Couchbase Console and then Settings->Sample Buckets.
- Create the following buckets:
- "default" - a Couchbase bucket with no password
- "authenticated" - a Couchbase bucket with a password of "secret"
- "memcached" - a Memcached bucket with no password
- Install an SSL certificate (copied from the Couchbase console Security->Root Certificate)
- A default primary index configured on the following buckets:
default,authenticated,beer-sampleandtravel-sample(egcreate primary index on `default`) - Add an FTS index to the
travel-samplebucket calledidx-travel - Update config.json with the hostname of your Couchbase Server IP and set enhancedAuth to
false - Update app.config's hostname and basic Couchbase client section with the Couchbase Server IP
Couchbase Server 5.0+ - In addition to the steps above:
- "ephemeral" - an Ephemeral bucket
- Update config.json enhancedAuth to
true - A user called
authenticatedwith a password ofsecret
NOTE: Couchbase Server 5.0+ uses Role-Based Access Control (RBAC) for authentication. This supersedes configuring bucket passwords with discrete users with their own passwords and offers much more granular control.
Please checkout this README for how to generate the gRPC proxies and stubs for Protostellar.
Being an Open Source project, the Couchbase SDK depends upon feedback and submissions from the community. If you feel as if you want to submit a bug fix or a feature, please post a Pull Request (PR). The PR will go through a formal code review process and merged after being approved by a Couchbase Engineer. In order to accept a submission, Couchbase requires that all contributors sign the Contributor License Agreement (CLA). When you push a PR, you will be prompted to sign the CLA.
Once the CLA is signed, you will be able to open the PR and one or more Couchbase engineers will review the submission. If it looks good, they will accept the PR and merge it with master. Note that is strongly encouraged to submit a Unit Test with each submission and also include a description of the submission, what changed and what the result is.