Merge pull request #434 from qdrant/feat/bashofmann/improve-installat…

…ion-docs

Improve installation docs

qdrant-landing/content/documentation/guides/configuration.md

@@ -17,22 +17,7 @@ production mode, you could also choose to overwrite `config/production.yaml`.
 See [ordering](#order-and-priority) for details on how configurations are
 loaded.
 
-To use Qdrant in Docker and overwrite the production configuration use:
-
-```bash
-docker run -p 6333:6333 \
-    -v $(pwd)/path/to/custom_config.yaml:/qdrant/config/production.yaml \
-    qdrant/qdrant
-```
-
-Or use your own configuration file and specify it:
-
-```bash
-docker run -p 6333:6333 \
-    -v $(pwd)/path/to/custom_config.yaml:/qdrant/config/custom_config.yaml \
-    qdrant/qdrant \
-    ./qdrant --config-path config/custom_config.yaml
-```
+The [Installation](../installation) guide contains examples of how to set up Qdrant with a custom configuration for the different deployment methods.
 
 ## Order and priority
 

qdrant-landing/content/documentation/guides/installation.md

@@ -6,74 +6,189 @@ aliases:
   - ../installation
 ---
 
-# Installation options
+## Installation requirements
 
-## Docker
+The following sections describe the requirements for deploying Qdrant.
 
-The easiest way to start using Qdrant is to run it from a ready-made Docker image.
-The latest versions are always available on [DockerHub](https://hub.docker.com/r/qdrant/qdrant/tags?page=1&ordering=last_updated).
+### CPU and memory
+
+The CPU and RAM that you need depends on:
+
+- Number of vectors
+- Vector dimensions
+- [Payloads](/documentation/concepts/payload/) and their indexes
+- Storage
+- Replication
+- How you configure quantization
+
+Our [Cloud Pricing Calculator](https://cloud.qdrant.io/calculator) can help you estimate required resources without payload or index data.
+
+### Storage
+
+For persistent storage, Qdrant requires block-level access to storage devices with a [POSIX-compatible file system](https://www.quobyte.com/storage-explained/posix-filesystem/). Network systems such as [iSCSI](https://en.wikipedia.org/wiki/ISCSI) that provide block-level access are also acceptable.
+Qdrant won't work with [Network file systems](https://en.wikipedia.org/wiki/File_system#Network_file_systems) such as NFS, or [Object storage](https://en.wikipedia.org/wiki/Object_storage) systems such as S3.
+
+If you offload vectors to a local disk, we recommend you use a solid-state (SSD or NVMe) drive.
+
+### Networking
+
+Each Qdrant instance requires three open ports:
+
+* `6333` - For the HTTP API, for the [Monitoring](/documentation/guides/monitoring/) health and metrics endpoints
+* `6334` - For the [gRPC](documentation/interfaces/#grpc-interface) API
+* `6335` - For [Distributed deployment](/documentation/guides/distributed_deployment/)
+
+All Qdrant instances in a cluster must be able to:
+
+- Communicate with each other over these ports
+- Allow incoming connections to ports `6333` and `6334` from clients that use Qdrant.
+
+## Installation options
+
+Qdrant can be installed in different ways depending on your needs:
+
+For production, you can use our Qdrant Cloud to run Qdrant either fully managed in our infrastructure or with Hybrid SaaS in yours. 
 
-Make sure that Docker daemon is installed and running:
+For testing or development setups, you can run the Qdrant container or as a binary executable. 
+
+If you want to run Qdrant in your own infrastructure, without any cloud connection, we recommend to install Qdrant in a Kubernetes cluster with our Helm chart, or to use our Qdrant Enterprise Operator
+
+## Production
+
+For production, we recommend that you configure Qdrant in the cloud, with Kubernetes, or with a Qdrant Enterprise Operator.
+
+### Qdrant Cloud
+
+You can set up production with the [Qdrant Cloud](https://qdrant.to/cloud), which provides fully managed Qdrant databases. 
+It provides horizontal and vertical scaling, one click installation and upgrades, monitoring, logging, as well as backup and disaster recovery. For more information, see the [Qdrant Cloud documentation](/documentation/cloud).
+
+### Kubernetes
+
+You can use a ready-made [Helm Chart](https://helm.sh/docs/) to run Qdrant in your Kubernetes cluster:
 
 ```bash
-sudo docker info
+helm repo add qdrant https://qdrant.to/helm
+helm install qdrant qdrant/qdrant
 ```
 
-* If you do not see the server listed, start the Docker daemon.
-* On Linux, Docker needs `sudo` privileges. To run Docker commands without `sudo` privileges, create a docker group and add your users (see [Post-installation Steps for Linux](https://docs.docker.com/engine/install/linux-postinstall/) for details).
+For more information, see the [qdrant-helm](https://github.com/qdrant/qdrant-helm/tree/main/charts/qdrant) README.
+
+### Qdrant Kubernetes Operator
+
+We provide a Qdrant Enterprise Operator for Kubernetes installations. For more information, [use this form](https://qdrant.to/contact-us) to contact us.
+
+### Docker and Docker Compose
+
+Usually, we recommend to run Qdrant in Kubernetes, or use the Qdrant Cloud for production setups. This makes setting up highly available and scalable Qdrant clusters with backups and disaster recovery a lot easier.
+
+However, you can also use Docker and Docker Compose to run Qdrant in production, by following the setup instructions in the [Docker](#docker) and [Docker Compose](#docker-compose) Development sections. 
+In addition, you have to make sure:
+
+* To use a performant [persistent storage](#storage) for your data
+* To configure the [security settings](/documentation/guides/security/) for your deployment
+* To set up and configure Qdrant on multiple nodes for a highly available [distributed deployment](/documentation/guides/distributed_deployment/)
+* To set up a load balancer for your Qdrant cluster
+* To create a [backup and disaster recovery strategy](/documentation/concepts/snapshots/) for your data
+* To integrate Qdrant with your [monitoring](/documentation/guides/monitoring/) and logging solutions
+
+## Development
+
+For development and testing, we recommend that you set up Qdrant in Docker. We also have different client libraries.
+
+### Docker
+
+The easiest way to start using Qdrant for testing or development is to run the Qdrant container image.
+The latest versions are always available on [DockerHub](https://hub.docker.com/r/qdrant/qdrant/tags?page=1&ordering=last_updated).
+
+Make sure that [Docker](https://docs.docker.com/engine/install/), [Podman](https://podman.io/docs/installation) or the container runtime of your choice is installed and running. The following instructions use Docker.
 
 Pull the image:
 
 ```bash
 docker pull qdrant/qdrant
 ```
 
-Run the container:
+In the following command, revise `$(pwd)/path/to/data` for your Docker configuration. Then use the updated command to run the container:
 
 ```bash
 docker run -p 6333:6333 \
     -v $(pwd)/path/to/data:/qdrant/storage \
     qdrant/qdrant
 ```
 
-With this command, you will start a Qdrant instance with the default configuration.
-It will store all data in `./path/to/data` directory.
+With this command, you start a Qdrant instance with the default configuration.
+It stores all data in the `./path/to/data` directory.
 
 By default, Qdrant uses port 6333, so at [localhost:6333](http://localhost:6333) you should see the welcome message.
 
-## From source
-
-Qdrant is written in Rust and can be compiled into a binary executable.
-This installation method can be helpful if you want to compile Qdrant for a specific processor architecture or if you do not want to use Docker for some reason.
+To change the Qdrant configuration, you can overwrite the production configuration:
 
-Before compiling, make sure that the necessary libraries and the [rust toolchain](https://www.rust-lang.org/tools/install) are installed.
-The current list of required libraries can be found in the [Dockerfile](https://github.com/qdrant/qdrant/blob/master/Dockerfile).
+```bash
+docker run -p 6333:6333 \
+    -v $(pwd)/path/to/data:/qdrant/storage \
+    -v $(pwd)/path/to/custom_config.yaml:/qdrant/config/production.yaml \
+    qdrant/qdrant
+```
 
-Build Qdrant with Cargo:
+Alternatively, you can use your own `custom_config.yaml` configuration file:
 
 ```bash
-cargo build --release --bin qdrant
+docker run -p 6333:6333 \
+    -v $(pwd)/path/to/data:/qdrant/storage \
+    -v $(pwd)/path/to/custom_config.yaml:/qdrant/config/custom_config.yaml \
+    qdrant/qdrant \
+    ./qdrant --config-path config/custom_config.yaml
 ```
 
-After a successful build, the binary is available at `./target/release/qdrant`.
+For more information, see the [Configuration](/documentation/guides/configuration/) documentation.
+
+### Docker Compose
+
+You can also use [Docker Compose](https://docs.docker.com/compose/) to run Qdrant.
+
+Here is an example customized compose file for a single node Qdrant cluster:
+
+```yaml
+services:
+  qdrant:
+    image: qdrant/qdrant:v1.6.1
+    restart: always
+    container_name: qdrant
+    ports:
+      - 6333:6333
+      - 6334:6334
+    expose:
+      - 6333
+      - 6334
+      - 6335
+    configs:
+      - source: qdrant_config
+        target: /qdrant/config/production.yaml
+    volumes:
+      - ./qdrant_data:/qdrant_data
+
+configs:
+  qdrant_config:
+    content: |
+      log_level: INFO  
+```
 
-## Python client
+### From source
 
-In addition to the service itself, Qdrant has a distinct python client, which has some additional features compared to [clients](https://qdrant.tech/documentation/quick_start/#clients) generated from OpenAPI directly.
+Qdrant is written in Rust and can be compiled into a binary executable.
+This installation method can be helpful if you want to compile Qdrant for a specific processor architecture or if you do not want to use Docker.
+
+Before compiling, make sure that the necessary libraries and the [rust toolchain](https://www.rust-lang.org/tools/install) are installed.
+The current list of required libraries can be found in the [Dockerfile](https://github.com/qdrant/qdrant/blob/master/Dockerfile).
 
-To install this client, just run the following command:
+Build Qdrant with Cargo:
 
 ```bash
-pip install qdrant-client
+cargo build --release --bin qdrant
 ```
 
-## Kubernetes
-
-You can use a ready-made [Helm Chart](https://helm.sh/docs/) to run Qdrant in your Kubeternetes cluster.
+After a successful build, you can find the binary in the following subdirectory `./target/release/qdrant`.
 
-```bash
-helm repo add qdrant https://qdrant.to/helm
-helm install qdrant-release qdrant/qdrant
-```
+## Client libraries
 
-Read further instructions in [qdrant-helm](https://github.com/qdrant/qdrant-helm) repository.
+In addition to the service, Qdrant provides a variety of client libraries for different programming languages. For a full list, see our [Client libraries](../../interfaces/#client-libraries) documentation.

qdrant-landing/content/documentation/interfaces.md

@@ -13,7 +13,7 @@ or [protobuf](https://github.com/qdrant/qdrant/tree/master/lib/api/src/grpc/prot
 ||Client Repository|Installation|Version|
 |-|-|-|-|
 |[![python](/docs/misc/python.webp)](https://python-client.qdrant.tech/)|**[Python](https://github.com/qdrant/qdrant-client)**|`pip install qdrant-client[fastembed]`|**Latest Release**, [API Docs](https://python-client.qdrant.tech/)|
-|![typescript](/docs/misc/ts.webp)|**[Typescript](https://github.com/qdrant/qdrant-js)**|`npm install @qdrant/js-client-rest`|**Latest Release**|
+|![typescript](/docs/misc/ts.webp)|**[JavaScript / Typescript](https://github.com/qdrant/qdrant-js)**|`npm install @qdrant/js-client-rest`|**Latest Release**|
 |![rust](/docs/misc/rust.webp)|**[Rust](https://github.com/qdrant/rust-client)**|`cargo add qdrant-client`|**Latest Release**|
 |![golang](/docs/misc/go.webp)|**[Go](https://github.com/qdrant/go-client)**|`go get github.com/qdrant/go-client`|**Latest Release**|
 |![.net](/docs/misc/dotnet.webp)|**[.NET](https://github.com/qdrant/qdrant-dotnet)**|`dotnet add package Qdrant.Client`|**Latest Release**|