openreplay

History

Rajesh Rajendran f823ce13ed chore(deploy): optional nginx https redirect Signed-off-by: Rajesh Rajendran <rjshrjndrn@gmail.com>		2021-05-17 22:38:11 +05:30
..
helm	chore(deploy): optional nginx https redirect	2021-05-17 22:38:11 +05:30
certbot.sh	fix(certbot): proper home directory handling	2021-05-12 11:55:03 +05:30
README.md	Update README.md	2021-05-17 15:35:57 +02:00

README.md

Installing OpenReplay on any VM (Debian based, preferably Ubuntu 20.04)

You can start testing OpenReplay by installing it on any VM (at least 2 vCPUs, 8 GB of RAM and 50 GB of storage). We'll initialize a single node kubernetes cluster with k3s and install OpenReplay on the cluster.

cd helm && bash install.sh

Installing OpenReplay on Kubernetes

OpenReplay runs 100% on kubernetes. So if you've got a kubernetes cluster, preferably, a cluster dedicated to OpenReplay (on a single node of 4 vCPUs, 8 GB of RAM and 50 GB of storage). You can run the script, which internally uses helm to install OpenReplay.

We hope your cluster has provision to create a service type LoadBalancer for exposing OpenReplay on the internet.

cd helm && bash kube-install.sh

Management of OpenReplay apps

openreplay-cli:

This script will help to manage OpenReplay applications. Basic operations covered are
- status: status of the applications
- logs: logs of a specific application
- stop: stop one or all services
- start: start one or all services
- restart: restart one or all services
For more information:
```
cd helm && openreplay-cli -h
```