Couchbase CMD Tools

[Francis Varga]

Hi is there a seperated package for the CMD Tools?

like couchbase-cmd.dpkg? :)

[Sergey Avseyev]

You can use

brew install libcouchbase

To install 1.x version or Couchbase fork for most recent. couchbase.com/develop/c/next

-- Sergey Avseyev

On 25 Oct 2012 15:27, "Francis Varga" <francis...@googlemail.com> wrote:

Hi is there a seperated package for the CMD Tools?

like couchbase-cmd.dpkg? :)

--
Couchbase 2.0 Beta: http://www.couchbase.com/couchbase-server/beta
Couchbase 2.0 Manual: http://www.couchbase.com/docs/couchbase-manual-2.0/
Couchbase 2.0 Wiki: http://www.couchbase.com/wiki/display/couchbase/Couchbase+Server+2.0
Couchbase Forums: http://www.couchbase.com/forums/
---
You received this message because you are subscribed to the Google Groups "Couchbase Team 8091" group.
To post to this group, send email to couchba...@googlegroups.com.
To unsubscribe from this group, send email to couchbase-809...@googlegroups.com.
Visit this group at http://groups.google.com/group/couchbase-8091?hl=en.
To view this discussion on the web visit https://groups.google.com/d/msg/couchbase-8091/-/QrHHye1GF5YJ.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Francis Varga]

ah damn the tag was a little bit wrong :).

I mean:

cbbackup

cbrestore

cbstats

cbtransfer

[Sergey Avseyev]

Libcouchbase tools has stats too :-)

-- Sergey Avseyev

[MC Brown]

When installing you should be prompted to install links to the tools in a directory of your choice.

If not, you can do so from the menu item (Install Command-line tools…).

Finally, you can always access them directly within the app package:

/Applications/Couchbase Server.app/Contents/Resources/couchbase-core/bin

MC

On 25 Oct 2012, at 13:27, Francis Varga <francis...@googlemail.com> wrote:

> Hi is there a seperated package for the CMD Tools?
>
> like couchbase-cmd.dpkg? :)
>
>
>

> --
> Couchbase 2.0 Beta: http://www.couchbase.com/couchbase-server/beta
> Couchbase 2.0 Manual: http://www.couchbase.com/docs/couchbase-manual-2.0/
> Couchbase 2.0 Wiki: http://www.couchbase.com/wiki/display/couchbase/Couchbase+Server+2.0
> Couchbase Forums: http://www.couchbase.com/forums/
> ---
> You received this message because you are subscribed to the Google Groups "Couchbase Team 8091" group.
> To post to this group, send email to couchba...@googlegroups.com.
> To unsubscribe from this group, send email to couchbase-809...@googlegroups.com.
> Visit this group at http://groups.google.com/group/couchbase-8091?hl=en.
> To view this discussion on the web visit https://groups.google.com/d/msg/couchbase-8091/-/QrHHye1GF5YJ.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--

MC Brown, VP, Technical Publications and Education
m...@couchbase.com
Skype: mcmcslp
Mobile: +44 7411 295711 (GMT)

[Francis Varga]

yes but i have to installed the couchbase. i wanted to run a micro instance for our backups.

so i can create a cronjob which runs and backup our cluster and store it into the S3.

[MC Brown]

Ah, I follow you now :)

Yes, you'll need to install Couchbase. But you wont need to actually run Couchbase on that machine to make use of the command-line tools. On Linux, run the installer package as normal, but then shutdown the Couchbase instance that is created:

/etc/init.d/couchbase-server stop

You can do that before you even go through the setup. You'll probably also want to remove it from the boot scripts too.

You have to specify the cluster IP and authentication on each request on the command-line, and that IP can be remote.

[Perry Krug]

You also don't really need to install the whole server, just grab the /opt/couchbase/lib/python directory and copy it to whatever machine you want...I believe that should contain everything you need to run the tools.  There might be a few other pieces, but you don't need the whole /opt/couchbase nor do you need to do an actual install.

Perry Krug

perr...@gmail.com

[MC Brown]

Copying /opt/couchbase/lib/python alone will not work.

You also need the libraries in /opt/couchbase/lib, otherwise the Python tools on their own don't work.

It starts getting completed to pick only the pieces you need compared to using dpkg/rpm.

[Ken Williams]

We've broken this out into it's own rpm. If there's interest I'll post my spec file when I am back at home next week. It's a little subjective whether you need/want to do this or not anyway. Maintaining yet another rpm just for the sake of saving some small amount of disk space might not be worth the effort. I had a couple wrapper scripts that I bundled along with it, internal tools that we use, so it made sense to make it a complete stand alone package. You can argue the value in either direction, ultimately it's up to you if you want to go that route. In general it's probably better to just install the whole thing however.