CBC(1)
💅 CBC(1) 💅
okay so bestie, sit down, grab a strawberry lemonade 🍓, because we're about to get so acquainted with cbc — the Couchbase Client Commandline Utility. She's a whole queen, she talks to Couchbase clusters, and she's about to be your main character energy at 3am when prod is doing prod things. No cap. 💖
✨ NAME ✨
cbc — the Couchbase Client Commandline Utility. That's her full government name, periodt. 👑
🌈 SYNOPSIS 🌈
here's the vibe check on how you call her:
cbc COMMAND [OPTIONS]
cbc help
cbc version
cbc cat KEYS ...... [OPTIONS]
cbc create KEY -V VALUE [OPTIONS]
cbc create KEY [OPTIONS]
cbc cp FILES ...... [OPTIONS]
cbc incr KEY [OPTIONS]
cbc decr KEY [OPTIONS]
cbc touch KEY [OPTIONS]
cbc rm KEY [OPTIONS]
cbc hash KEY [OPTIONS]
cbc stats KEYS ...... [OPTIONS]
cbc observe KEYS ...... [OPTIONS]
cbc view VIEWPATH [OPTIONS]
cbc lock KEY [OPTIONS]
cbc unlock KEY CAS [OPTIONS]
cbc admin -P PASSWORD RESTAPI [OPTIONS]
cbc bucket-list -P PASSWORD [OPTIONS]
cbc bucket-create -P PASSWORD NAME [OPTIONS]
cbc bucket-delete -P PASSWORD NAME [OPTIONS]
cbc bucket-flush NAME [OPTIONS]
cbc role-list [OPTIONS]
cbc user-list [OPTIONS]
cbc user-upsert NAME [OPTIONS]
cbc user-delete NAME [OPTIONS]
cbc connstr SPEC
cbc query QUERY ...... [OPTIONS]
cbc write-config [OPTIONS ......]
cbc strerror HEX-OR-DECIMAL-CODE
cbc ping [OPTIONS ......]
cbc watch [KEYS ......] [OPTIONS ......]
cbc keygen [KEYS ......] [OPTIONS ......]see how she's got a different outfit for every occasion? 🎀
🦋 DESCRIPTION 🦋
cbc is a utility for communicating with a Couchbase cluster. like, that's her whole job. her nine-to-five. her brand. ✨
The way you use her is: command name first, and then a series of command options appropriate for that specific command. command first, options after — she's very particular about the order, bestie, it's giving Virgo.
And if you ever forget what she can do (no judgment, it happens 😭), cbc help will always show you the full list of available commands. she's not gatekeeping. she would NEVER gatekeep. 💖
💖 OPTIONS 💖
Options may be read either from the command line, or from a configuration file — see cbcrc(4). so yes, you can make her remember your preferences. that's self-care. 🎀
The following common options may be applied to most of the commands:
@@common-options.markdown@@
🌟 ADDITIONAL OPTIONS 🌟
okay so here's the fun part — you can sneak these in through the connection string too. The following options may be included in the connection string (via the -U option) as URI-style query params:
couchbase://host/bucket?option1=value1&option2=value2…or as individual key=value pairs passed to the -D switch, like this:
-Doption1=value1 -Doption2=valueThe -D will internally build the connection string, and is provided as a convenience for options to be easily passed on the command-line. she's doing the formatting for you because she's a considerate queen. 💅
@@common-additional-options.markdown@@
👑 COMMANDS 👑
The following commands are supported by cbc. Unless otherwise specified, each command supports all of the options above. yes, ALL of them. she shares. 🫶
🐱 cat
Write the value of keys to standard output.
This command requires that at least one key may be passed to it, but may accept multiple keys. The keys should be specified as positional arguments after the command. so it's cbc cat KEY1 KEY2 KEY3 — put them after, not before. she's not flexible on this one.
In addition to the options in the OPTIONS section, the following options are supported:
-r,--replica=all|INDEX— Read the value from a replica server. The value for this option can either be the stringall, which will cause the client to request the value from each replica, orINDEX, whereINDEXis a 0-based replica index. 0-based, bestie, don't come in here with your 1s.-e,--expiry=EXPIRATION— Specify that this operation should be a get-and-touch operation, in which the key's expiry time is updated along with retrieving the item. get AND touch. multitasking icon. ✨
🎀 create & cp
Create a new item in the cluster, or update the value of an existing item. By default this command will read the value from standard input unless the --value option is specified.
The cp command functions the same, except it operates on a list of files. Each file is stored in the cluster under the name specified on the command line. so like, name your file something sensible. she's using that filename as the key, no takebacks. 🍓
In addition to the options in the OPTIONS section, the following options are supported:
-V,--value=VALUE— The value to store in the cluster. If omitted, the value is read from standard input. This option is valid only for thecreatecommand. only create. not cp. she said what she said.-f,--flags=ITEMFLAGS— A 32 bit unsigned integer to be stored alongside the value. This number is returned when the item is retrieved again. Other clients commonly use this value to determine the type of item being stored. it's like a lil name tag for your data. cute.-e,--expiry=EXPIRATION— The number of time in seconds from now at which the item should expire. seconds. from now. she's counting down. ⏳-M,--mode=upsert|insert|replace— Specify the storage mode. Mode can be one ofinsert(store item if it does not yet exist),replace(only store item if key already exists), orupsert(unconditionally store item). pick your fighter. 💅-d,--durability=LEVEL— Specify durability level for mutation operations. Known values are:"none","majority","majority_and_persist_to_active","persist_to_majority".-p,--persist-to=NUMNODES— Wait until the item has been persisted to at leastNUMNODESnodes' disk. IfNUMNODESis1then wait until only the master node has persisted the item for this key. You may not specify a number greater than the number of nodes actually in the cluster. do NOT try to be cute and put a number bigger than your actual node count, she will not be amused. 💀-r,--replicate-to=NREPLICAS— Wait until the item has been replicated to at leastNREPLICASreplica nodes. The bucket must be configured with at least one replica, and at leastNREPLICASreplica nodes must be online. replicas gotta exist AND be online. both. that's the rule.
🔍 observe
Retrieve persistence and replication information for items.
This command will print the status of each key to standard error. standard ERROR, bestie, not stdout. don't pipe it into the wrong place and then come crying to me. 😭
See the OPTIONS for accepted options.
➕ incr & ➖ decr
These commands increment or decrement a counter item in the cluster. A counter is a value stored as an ASCII string which is readable as a number — thus, for example, 42. she's a number. she's stored as text. she's doing her best. 🌸
These commands will by default refuse to operate on an item which does not exist in the cluster. no item? no operation. periodt. she's not creating something out of nothing.
The incr and decr command differ with how they treat the --delta argument. The incr command will treat the value as a positive offset and increment the current value by the amount specified, whereas the decr command will treat the value as a negative offset and decrement the value by the amount specified. same option, opposite directions. it's giving mirror twins. 🦋
In addition to OPTIONS, the following options are supported:
--initial=_DEFAULT_— Set the initial value for the item if it does not exist in the cluster. The value should be an unsigned 64 bit integer. If this option is not specified and the item does not exist, the operation will fail. If the item does exist, this option is ignored. ignored. like she didn't even see it. 🙈--delta=DELTA— Set the absolute delta by which the value should change. If the command isincrthen the value will be incremented by this amount. If the command isdecrthen the value will be decremented by this amount. The default value for this option is1. default 1. baby steps. adorable.-e,--expiry=EXPIRATION— Set the expiration time for the key, in terms of seconds from now.
🗺️ hash
Display mapping information for a key.
This command diplays mapping information about a key. The mapping information indicates which vBucket the key is mapped to, and which server is currently the master node for the given vBucket. where does your key LIVE. who's her landlord. this is the command that tells you. 🏠
See the OPTIONS for accepted options.
🔒 lock
Lock an item in the cluster.
This will retrieve and lock an item in the cluster, making it inaccessible for modification until it is unlocked (see unlock). she is HERS now. nobody touches her. not until you unlock her. 🔐
In addition to the common options (OPTIONS), this command accepts the following options:
-e,--expiry=LOCKTIME— Specify the amount of time the lock should be held for. If not specified, it will default to the server side maximum of 15 seconds. 15 seconds, that's the ceiling, don't fight the server, she sets the rules. ⏰
🔓 unlock
Unlock a previously locked item.
This command accepts two mandatory positional arguments which are the key and the CAS value. The CAS value should be specified as printed from the lock command — i.e. with the leading 0x hexadecimal prefix. keep that 0x prefix, bestie, I'm serious. strip it and she won't recognize the CAS. 💀
See the OPTIONS for accepted options.
🗑️ rm
Remove an item from the cluster.
This command will remove an item from the cluster. If the item does not exist, the operation will fail. no silent nothing. she wants you to know. ✨
See the OPTIONS for accepted options.
📊 stats
Retrieve a list of cluster statistics. If positional arguments are passed to this command, only the statistics classified under those keys will be retrieved. See the server documentation for a full list of possible statistics categories. categories, bestie, go read the server docs for the full menu. 🍓
This command will contact each server in the cluster and retrieve that node's own set of statistics. every single node. she's thorough. 💅
The statistics are printed to standard output in the form of:
SERVER STATISTIC VALUEwhere SERVER is the host:port representation of the node which has provided this statistic, STATISTIC is the name of the current statistical key, and VALUE is the value for this statistic.
See the OPTIONS for accepted options.
👀 watch
Retrieve a list of cluster statistics, select specified sub-keys and aggregate values across the cluster. Then continuously poll the stats and display the difference with the previous values. If the list of stat sub-keys is not specified, the command will use cmd_total_ops, cmd_total_gets, cmd_total_sets. she just keeps watching. forever. like a very dedicated mutual who never sleeps. 🔥
In addition to the options in the OPTIONS section, the following options are supported:
-n,--interval=VALUE— Update interval in seconds (default1second).
🔑 keygen
Output list of keys that equally distribute amongst every vbucket. perfectly balanced. as all things should be. ⚖️
In addition to the options in the OPTIONS section, the following options are supported:
--keys-per-vbucket=VALUE— Number of keys to generate per vBucket (default1).
📝 write-config
Write the configuration file based on arguments passed. she's writing it down so she remembers. organized queen. 🎀
🐛 strerror
Decode library error code. that cryptic number? she'll translate. iykyk. 🔍
⭐ version
Display information about the underlying version of libcouchbase to which the cbc binary is linked. know your roots, bestie. 💖
🔊 verbosity
Set the memcached logging versbosity on the cluster. This affects how the memcached processes write their logs. This command accepts a single positional argument which is a string describing the verbosity level to be set. The options are detail, debug info, and warning. pick one. she's not doing combos. ✨
🏓 ping
Sends NOOP-like request to every service on each cluster node, and report time it took to response. a little "u up?" to the whole cluster. 🌈
--details— Provide more details about status of the service.-t,--table— Render results as a table.
👁️ view
Execute an HTTP request against the server's view (CAPI) interface.
The request may be one to create a design document, view a design document, or query a view.
To create a design document, the definition of the document (in JSON) should be piped to the command on standard input. pipe it in, bestie, don't try to type a whole design doc by hand. 😭
This command accepts one positional argument which is the path (relative to the bucket) to execute. Thus, to query the brewery_beers view in the beer design document within the beer-sample bucket, one would do:
cbc view -U couchbase://localhost/beer-sample _design/beer/_view/brewery_beersIn addition to the OPTIONS specified above, the following options are recognized:
-X,--method=GET|PUT|POST|DELETE— tells cbc which HTTP method to use for this specific request. Default isGET, which is the one you want when you're querying a view. Deleting a design document that already exists? That'sDELETE. Creating a shiny new design document? That'sPUT. no notes, iconic behavior 💅
🍓 query — go run a N1QL query
Runs a N1QL Query. Important vibe check: the cluster needs to have at least one query node enabled, otherwise this is just gonna sit there looking at you.
You pass the query itself as a positional argument on the command line. The query is allowed to contain named placeholders — those look like $param — and you can hand over their values later using the --qarg='$param=value' syntax.
bestie pls put your statement in single quotes. That keeps your shell from doing expansion nonsense to it and ruining your whole day. 🫶
On top of all the OPTIONS we already covered above, query also recognizes these:
-Q,--qopt=SETTING=VALUE— throw in extra options that control how the query actually executes. Classic use case: setting thescan_consistencyof the query.-A,--qarg=PLACEHOLDER=VALUE— feed values to the placeholders you left in your query string. Heads up: those placeholder values have to evaluate to valid JSON values. ⭐--prepare— prepare the query before issuing it. Default isFALSE.--analytics— run the query against the analytics service instead. Default isFALSE.
👑 admin — talk straight to the management REST API
Fires off an administrative request against the management REST API. iykyk: to actually pull off an administrative API call you have to give cbc admin administrative credentials — meaning the username and password you'd use to log into the administration console. No shortcuts here.
This command takes exactly one positional argument, and that argument is the REST API endpoint — i.e. the HTTP path — you want to hit.
If the request needs a body, you supply it via standard input. 📥
On top of the OPTIONS above, it also recognizes:
-X,--method=GET|PUT|POST|DELETE— which HTTP method to use for this specific request. The default method isGET.
🎀 bucket-list — show me the buckets
Lists the buckets in the cluster. Simple. Clean. We love her.
On top of the OPTIONS above, it also recognizes:
-r,--raw— print the unformatted server response in JSON form.
🦋 bucket-create — make a new bucket
Creates a bucket in the cluster. ✨
This command creates a bucket whose name is the lone positional argument on the command line.
Since this is an administrative command, you should be supplying administrative credentials through the --username and --password options.
On top of the OPTIONS above, it also recognizes:
--bucket-type=couchbase|memcached— what kind of bucket to create. Acouchbasebucket has persistence to disk and replication. Amemcachedbucket is in-memory only and does not replicate.--ram-quota=QUOTA— the maximum amount of memory the bucket should occupy (per node), in megabytes. If you don't specify it, the default is512.--bucket-password=PASSWORD— the password that locks this bucket down. If you pass one, every client trying to connect to the bucket will need it. If you leave it out, the bucket may be accessible to everyone for both read and write access. yes, literally everyone, so think about it fr fr 🙈--num-replicas=REPLICAS— how many replicas the bucket should have. This sets the number of nodes each item gets replicated to. If you don't specify it, the default is1.
🌈 bucket-flush — wipe a bucket clean
Flushes the bucket whose name is the lone positional argument on the command line.
Cute detail: this command does not require administrative level credentials — but it does require that flush be enabled for the bucket. if flush isn't enabled, this is not happening, periodt.
See the OPTIONS for the accepted options.
💜 role-list — who can do what
Lists the accessible RBAC user roles in the cluster. 🎀
On top of the OPTIONS above, it also recognizes:
-r,--raw— print the unformatted server response in JSON form.
🧚 user-list — the whole guest list
Lists users in the cluster.
On top of the OPTIONS above, it also recognizes:
-r,--raw— print the unformatted server response in JSON form.
💖 user-upsert — create or update a user
Creates or updates a user in the cluster. Takes the user ID as an argument.
On top of the OPTIONS above, it also recognizes:
--domain=local|remote— the domain where the user account is defined. If you don't specify it, the default islocal.--full-name=FULL_NAME— the user's fullname. If you don't specify it, the default is an empty string.--role=ROLE— the role associated with the user. You can specify this multiple times if you need to. 👑--user-password=PASSWORD— the password for the user.
🩷 user-delete — bye bye user
Deletes a user in the cluster. Takes the user ID as an argument.
On top of the OPTIONS above, it also recognizes:
--domain=local|remote— the domain where the user account is defined. If you don't specify it, the default islocal.
⭐ connstr — break a connection string down
Parses a connection string into its constituent parts and displays them on the screen. The command takes a single positional argument, which is the string to parse. 🦋
✨ EXAMPLES ✨
okay bestie this is the part where it all clicks 💖 these are real actual command lines you can copy, paste and slay with.
🌈 CONNECTION EXAMPLES
here's how you link up with literally every type of bucket. all of these are just grabbing the key key — peep OPERATION EXAMPLES down below if you wanna know what the individual sub-commands actually do. 🦋
Connect to a bucket (a_bucket) on a cluster on a remote host (for servers version 5.x+). It uses account 'myname' and asks password interactively:
cbc cat key -U couchbase://192.168.33.101/a_bucket -u myname -P-Run against a password-less bucket (a_bucket) on a cluster on a remote host (for servers older than 5.x):
cbc cat key -U couchbase://192.168.33.101/a_bucketConnect to an SSL cluster at secure.net. The certificate for the cluster is stored locally at /home/couchbase/couchbase_cert.pem:
cbc cat key -U couchbases://secure.net/topsecret_bucket?certpath=/home/couchbase/couchbase_cert.pemConnect to an SSL cluster at secure.net, ignoring certificate verification. This is insecure but handy for testing:
cbc cat key -U couchbases://secure.net/topsecret_bucket?ssl=no_verifyConnect to a password protected bucket (protected) on a remote host (for servers older than 5.x):
cbc cat key -U couchbase://remote.host.net/protected -P-
Bucket password:Connect to a password protected bucket (for servers older than 5.x), specifying the password on the command line (INSECURE, but useful for testing dummy environments)
cbc cat key -U couchbase://remote.host.net/protected -P t0ps3cr3tConnect to a bucket running on a cluster with a custom REST API port
cbc cat key -U http://localhost:9000/defaultConnect to a bucket running on a cluster with a custom memcached port
cbc cat key -U couchbase://localhost:12000/defaultConnect to a memcached (http://memcached.org) cluster using the binary protocol. A vanilla memcached cluster is not the same as a memcached bucket residing within a couchbase cluster (use the normal couchbase:// scheme for that):
cbc cat key -U memcached://host1,host2,host3,host4Connect to a cluster using the HTTP protocol for bootstrap, and set the operation timeout to 5 seconds
cbc cat key -U couchbase://host/bucket -Dbootstrap_on=http -Doperation_timeout=5🎀 OPERATION EXAMPLES
Store a file to the cluster:
$ cbc cp mystuff.txt
mystuff.txt Stored. CAS=0xe15dbe22efc1e00Retrieve persistence/replication information about an item (note that Status is a set of bits):
$ cbc observe mystuff.txt
mystuff [Master] Status=0x80, CAS=0x0Display mapping information about keys:
$cbc hash foo bar baz
foo: [vBucket=115, Index=3] Server: cbnode3:11210, CouchAPI: http://cbnode3:8092/default
bar: [vBucket=767, Index=0] Server: cbnode1:11210, CouchAPI: http://cbnode1:8092/default
baz: [vBucket=36, Index=2] Server: cbnode2:11210, CouchAPI: http://cbnode2:8092/defaultCreate a bucket:
$ cbc bucket-create --bucket-type=memcached --ram-quota=100 --password=letmein -u Administrator -P 123456 mybucket
Requesting /pools/default/buckets
202
Cache-Control: no-cache
Content-Length: 0
Date: Sun, 22 Jun 2014 22:43:56 GMT
Location: /pools/default/buckets/mybucket
Pragma: no-cache
Server: Couchbase ServerFlush a bucket:
$ cbc bucket-flush default
Requesting /pools/default/buckets/default/controller/doFlush
200
Cache-Control: no-cache
Content-Length: 0
Date: Sun, 22 Jun 2014 22:53:44 GMT
Pragma: no-cache
Server: Couchbase ServerDelete a bucket:
$ cbc bucket-delete mybucket -P123456
Requesting /pools/default/buckets/mybucket
200
Cache-Control: no-cache
Content-Length: 0
Date: Sun, 22 Jun 2014 22:55:58 GMT
Pragma: no-cache
Server: Couchbase ServerUse cbc stats to determine the minimum and maximum timeouts for a lock operation:
$ cbc stats | grep ep_getl
localhost:11210 ep_getl_default_timeout 15
localhost:11210 ep_getl_max_timeout 30Create a design document:
$ echo '{"views":{"all":{"map":"function(doc,meta){emit(meta.id,null)}"}}}' | cbc view -X PUT _design/blog
201
Cache-Control: must-revalidate
Content-Length: 32
Content-Type: application/json
Date: Sun, 22 Jun 2014 23:03:40 GMT
Location: http://localhost:8092/default/_design/blog
Server: MochiWeb/1.0 (Any of you quaids got a smint?)
{"ok":true,"id":"_design/blog"}Query a view:
$ cbc view _design/blog/_view/all?limit=5
200
Cache-Control: must-revalidate
Content-Type: application/json
Date: Sun, 22 Jun 2014 23:06:09 GMT
Server: MochiWeb/1.0 (Any of you quaids got a smint?)
Transfer-Encoding: chunked
{"total_rows":20,"rows":[
{"id":"bin","key":"bin","value":null},
{"id":"check-all-libev-unit-tests.log","key":"check-all-libev-unit-tests.log","value":null},
{"id":"check-all-libevent-unit-tests.log","key":"check-all-libevent-unit-tests.log","value":null},
{"id":"check-all-select-unit-tests.log","key":"check-all-select-unit-tests.log","value":null},
{"id":"cmake_install.cmake","key":"cmake_install.cmake","value":null}
]
}Issue a N1QL query:
$ cbc query 'SELECT * FROM `travel-sample` WHERE type="airport" AND city=$city' -Qscan_consistency=request_plus -A'$city=\"Reno\"'Ping cluster services:
$ cbc ping --details -Ucouchbase://192.168.1.101
{
"version" : 1,
"config_rev" : 54,
"id" : "0x1d67af0",
"sdk" : "libcouchbase/2.8.4",
"services" : {
"fts" : [
{
"id" : "0x1d75e90",
"latency_us" : 1500,
"local" : "192.168.1.12:35232",
"remote" : "192.168.1.101:8094",
"status" : "ok"
},
{
"id" : "0x1da6800",
"latency_us" : 2301,
"local" : "192.168.1.12:40344",
"remote" : "192.168.1.103:8094",
"status" : "ok"
},
{
"id" : "0x1da3270",
"latency_us" : 2820,
"local" : "192.168.1.12:42730",
"remote" : "192.168.1.102:8094",
"status" : "ok"
},
{
"details" : "LCB_ENETUNREACH (0x31): The remote host was unreachable - is your network OK?",
"latency_us" : 3071733,
"remote" : "192.168.1.104:8094",
"status" : "error"
}
],
"kv" : [
{
"id" : "0x1d6bde0",
"latency_us" : 3700,
"local" : "192.168.1.12:42006",
"remote" : "192.168.1.101:11210",
"scope" : "default",
"status" : "ok"
},
{
"id" : "0x1dadcf0",
"latency_us" : 5509,
"local" : "192.168.1.12:39936",
"remote" : "192.168.1.103:11210",
"scope" : "default",
"status" : "ok"
},
{
"id" : "0x1dac500",
"latency_us" : 5594,
"local" : "192.168.1.12:33868",
"remote" : "192.168.1.102:11210",
"scope" : "default",
"status" : "ok"
},
{
"latency_us" : 2501688,
"remote" : "192.168.1.104:11210",
"scope" : "default",
"status" : "timeout"
}
],
"n1ql" : [
{
"id" : "0x1d7f280",
"latency_us" : 3235,
"local" : "192.168.1.12:54210",
"remote" : "192.168.1.101:8093",
"status" : "ok"
},
{
"id" : "0x1d76f20",
"latency_us" : 4625,
"local" : "192.168.1.12:58454",
"remote" : "192.168.1.102:8093",
"status" : "ok"
},
{
"id" : "0x1da44b0",
"latency_us" : 4477,
"local" : "192.168.1.12:36678",
"remote" : "192.168.1.103:8093",
"status" : "ok"
},
{
"details" : "LCB_ENETUNREACH (0x31): The remote host was unreachable - is your network OK?",
"latency_us" : 3071843,
"remote" : "192.168.1.104:8093",
"status" : "error"
}
],
"views" : [
{
"id" : "0x1da55c0",
"latency_us" : 1762,
"local" : "192.168.1.12:52166",
"remote" : "192.168.1.103:8092",
"status" : "ok"
},
{
"id" : "0x1da20d0",
"latency_us" : 2016,
"local" : "192.168.1.12:59420",
"remote" : "192.168.1.102:8092",
"status" : "ok"
},
{
"id" : "0x1d6a740",
"latency_us" : 2567,
"local" : "192.168.1.12:38614",
"remote" : "192.168.1.101:8092",
"status" : "ok"
},
{
"details" : "LCB_ENETUNREACH (0x31): The remote host was unreachable - is your network OK?",
"latency_us" : 3071798,
"remote" : "192.168.1.104:8092",
"status" : "error"
}
]
}
}📁 FILES 📁
ngl this one is cute. cbc(1) and cbc-pillowfight(1) can both read options from cbcrc(4) 🫶
The default path for cbcrc is $HOME/.cbcrc, but you can override it by setting the CBC_CONFIG environment variable to an alternate path. ✨
💀 BUGS 💀
bestie listen to me. The options in this utility and their behavior are subject to change. 👀
This script should be used for experimentation only and not inside production scripts. no cap, do not put this in your prod pipeline, i am begging 🙏
👑 SEE ALSO 👑
🌸 History 🌸
The cbc command first appeared in version 0.3.0 of the library. It was significantly rewritten in version 2.4.0. glow-up of the century fr fr ✨💅
and that's the whole page bestie!! 🎀 this lil icon is from July 2024, and it's page CBC(1) of the manual — go forth and cbc responsibly, mwah 💖🦋🌈
📦 where this page comes from
- alpine 3.24: libcouchbase-doc 3.3.18-r0 · Apache-2.0
- fedora 43: libcouchbase-tools 3.3.17-2.fc43 · Apache-2.0
- fedora 44: libcouchbase-tools 3.3.18-3.fc44 · Apache-2.0
- nixos 26.05: libcouchbase 3.3.18
- nixpkgs unstable: libcouchbase 3.3.19
- 💖 girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms