Coder Social home page Coder Social logo

cockroachdb / docs Goto Github PK

View Code? Open in Web Editor NEW
181.0 54.0 448.0 324.93 MB

CockroachDB user documentation

Home Page: https://cockroachlabs.com/docs

License: Creative Commons Attribution 4.0 International

HTML 88.88% JavaScript 0.69% Shell 0.14% Go 1.19% Clojure 0.21% Python 1.21% Ruby 0.83% Java 2.85% C++ 0.20% PHP 0.21% Makefile 0.06% Rust 0.24% C# 0.53% Perl 0.01% SCSS 2.74%
hacktoberfest

docs's Introduction

CockroachDB Docs

This repository contains the source files for the CockroachDB documentation available at cockroachlabs.com/docs.

Suggest Improvements

Want a topic added to the docs? Need additional details or clarification? See an error or other problem? Please open an issue.

Write Docs

Want to contribute to the docs? See CONTRIBUTING for details about setting yourself up and getting started.

Resources

docs's People

Contributors

a-robinson avatar amruta-ranade avatar anagio avatar andf-crl avatar andreimatei avatar ashleykwtam avatar bdarnell avatar benesch avatar dbist avatar deronjohnson avatar eballeste avatar ericharmeling avatar florence-crl avatar gemma-shay avatar j-low avatar jseldess avatar kathancox avatar knz avatar lnhsingh avatar maddyblue avatar mdlinville avatar michaeltrestman avatar mikecrl avatar nickvigilante avatar rafiss avatar rmloveland avatar sploiselle avatar taroface avatar uptimedba avatar yzdocs avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

docs's Issues

cloud deployment

Instructions for deploying a multi-node cluster in the cloud (at least AWS).

prevent line-wrapping in code blocks

Currently, when a line of code is longer than than the screen allows, the line wraps. This makes certain samples harder to read.

Adjust the css to prevent line-wrapping; offer a horizontal scrollbar instead.

Add recommendations about file systems

So our product promises to behave nicely assuming the user is storing their files in a properly-behaved filesystem / persistent storage.

However as discussed in this paper: https://www.usenix.org/system/files/conference/osdi14/osdi14-paper-pillai.pdf

operating systems have bugs in how they implement file systems, and sometimes the OS promises that data written by an application is actually written to disk while there is a bug which causes this data to not be saved. Or the OS promises something about the order in which I/O operations issued by the DB are performed on disk, and instead actually does things in a different order. This is Real Bad.

Our docs need to explain what we assume from the underlying storage and make recommendations about which file systems are known to work sufficiently well.

Docs versioning

Figure out how to provide docs for multiple versions of CockroachDB

data types

Should be part of the SQL Reference section.

HTTPS

We need to get HTTPS working with the entire website. Currently it is returning a bad cert error. One solution would be to put cloudflare in front of the whole thing (my recommendation).

redirect docs. to /docs

It's pretty common for docs to be at docs.company.com, so we should make sure that when users go to docs.cockroachlabs.com, they get redirected to cockroachlabs.com/docs.

@mberhault, can you help with this at some point?

identifiers

To be part of the SQL reference section. Explain rules for identifiers and keywords.

cockroachdb compared to other dbs

Matrix comparing CockroachDB against other databases. Need to identify the most important points of comparison. Likely to included:

  • Horizontal scaling
  • Distributed transactions
  • ACID semantics
  • Strong consistency
  • SQL

@spencerkimball, @petermattis, @bdarnell: Can you help me identify other points of comparison as well as the dbs that we want to compare against?

Make all internal links relative

Making the links relative will make it easier to set up a staging environment as well as (automatically) testing before pushing upstream. Any thoughts?

add license

Add creative commons license.

Note from @bdarnell:

  • Attribution (CC BY): the most permissive license, and the closest to the apache software license
  • Attribution-ShareAlike (CC BY-SA): GPL-like, prevents closed derivatives of the docs
  • Attribution-NonCommercial (CC BY-NC): prevents others from e.g. publishing our docs in book form
  • Attribution-NoDerivs (CC BY-ND): prevents anything but a verbatim copy of the docs
  • Various combinations of ShareAlike, NonCommercial, NoDerivs

For comparison, mongodb's docs are under ShareAlike-NonCommercial; I checked cassandra/datastax and hbase but it was not immediately obvious what license their docs used. Tornado uses Attribution-only.

Note from @petermattis: The CC BY license sounds good to me. If Apache-style restrictions (or lack thereof) are good enough for our code they should be good enough for our docs.

Generic monitoring options

For users who don't use Prometheus, our 2.0 monitoring docs should probably cover:

  • The /health HTTP endpoint for node health.
  • The <hostname>:8080/_status/vars HTTP endpoint used by Prometheus. The format is easy-to-parse format, so users could massage the data to work with different monitoring system.
  • The raw JSON endpoints listed at <hostname>:8080/#/debug/, thought those pages are under construction and not exposed by default. To access them, you must first run SET CLUSTER SETTING server.remote_debugging.mode = 'any';.

@dianasaur323, any thoughts or comments?

start a local cluster

Instructions for starting a local cluster in various ways:

  • single node in dev mode (insecure)
  • single node secure
  • multi-node secure

Link away for starting up multi-node cluster across machines.

customize page-level toc

Our Jekyll theme has a built-in function to add a toc to the top of a page; you just add toc:true to the front-matter. Currently, it adds the toc to the very top of the page, above all other content. We should think about:

cc: @jess-edwards

install client drivers

Call out recommended postgres drivers (those we've tested) for:

  • python
  • ruby
  • go
  • c
  • javascript (node.js)
  • java
  • php
  • closure

Also mention that any postgres driver should work and suggest getting in touch if any problems.

frequently asked questions

Concise answers to questions we think prospects might be most immediately interested in, such as how does cockroach scale, how does it survive failures, why is is sql, etc.

cleanup bnf simplify/reduce

Currently the BNF generator has a few steps:

  1. Parse the sql.y yacc file
  2. Print a EBNF from it
  3. Parse the EBNF
  4. Simplify the EBNF
  5. Generate the RR diagrams with simplified EBNF

This is because before we had to use an external program for step 1. Now that we have our own parser, there's no need to convert to EBNF and back. Instead we can simplify the yacc AST in memory and only output an EBNF once.

add search

There needs to be a way to search across all topics in the docs.

Always planned to get it in there, but just occurred to me that this is pretty important for beta, @spencerkimball and @jess-edwards. Will look into options.

Update docs for starting cockroach - insecure and secure

Need to update Start a Local Cluster. See:

#4269 - see below
#4335 - default --stores value for cockroach start
#4352 - remove --dev mode for cockroach start

  • If cockroach start is specified then the server only listens on localhost and the server starts in insecure mode. This allows a developer running a local instance to start cockroach with no additional arguments.
  • If cockroach start --insecure is specified the server listens on all addresses and starts in insecure mode. This forces a production cockroach cluster composed of multiple nodes to explicitly specify --insecure.
  • If cockroach start --cert-file is specified the server listens on all addresses and starts in secure mode.

Try-Us-Out instructions should not use Docker, but binaries

You can't access http:\\<docker ip>:26527 because docker ports/networking something something. I think we need more to the docker invocation than what's documented here. I think @tschottdorf would know.

Also we need to figure out the relationship between the installation instructions we have in the README.md and the docs site.

install cockroachdb

  • Install instructions for Mac, Linux, and Windows.
  • Tab-type thing on page to show instructions only for relevant OS.

certificate and cert command usage

We should at the very least have the following:

  • overview of cockroach security settings (insecure vs full certs: both client and server)
  • for each cockroach cert command:
    • description of behavior
    • required files (eg: create-node and create-client need ca.crt and ca.key)
    • created files
    • equivalent openssl command and which fields are required for it to work

@mberhault will do a writeup and coordinate with @jseldess for integration into the docs.

build a test app

Show how to connect and perform basic sql commands from various language (python, ruby, c, javascript, go).

basic sql commands

Document most important sql commands for getting up and running with CockroachDB.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.