jan/openreplay
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix: renaming asayer in scripts/readme.md

Browse source 
Co-Authored-By: Mehdi Osman <estradino@users.noreply.github.com>
This commit is contained in:
Mehdi Osman 2021-05-12 20:52:27 +02:00
parent b4f9da404d
commit cc1a79f7b7
2 changed files with 24 additions and 25 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
ee/LICENSE.md
View file

@ -9,7 +9,7 @@ and are in compliance with, the OpenReplay Subscription Terms of Service, availa
at https://openreplay.com/terms.html (the “Enterprise Edition”), or other
agreement governing the use of the Software, as agreed by you and OpenReplay,
and otherwise have a valid OpenReplay Enterprise license for the
correct volume and number of seats. Subject to the foregoing sentence, you are free to
correct usage. Subject to the foregoing sentence, you are free to
modify this Software and publish patches to the Software. You agree that OpenReplay
and/or its licensors (as applicable) retain all right, title and interest in and
to all such modifications and/or patches, and all such modifications and/or

47
scripts/README.md
View file

@ -1,35 +1,34 @@
### Installing Asayer on any VM(Debian based, preferably Ubuntu 20.04)
### Installing OpenReplay on any VM (Debian based, preferably Ubuntu 20.04)
You can start testing Asayer by installing it on any VM ( ideally, 4core 16G ) machine.
We'll initialize a single node kubernetes cluster with [k3s](https://k3s.io) and install Asayer on the cluster.
```bash
cd helm && bash minimal-install.sh
```
### Installing Asayer on kubernetes cluster
Asayer runs 100% on kubernetes. So if you've got a kubernetes cluster, preferably, a cluster dedicated to asayer(even a single node 4core 16G node),
You can run the script, which internally uses helm to install Asayer.
We hope your cluster has provision to create a [service type](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer) `LoadBalancer` for exposing Asayer on internet.
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](https://k3s.io) and install OpenReplay on the cluster.
```bash
cd helm && bash install.sh
```
### Management of Asayer apps
### Installing OpenReplay on Kubernetes
- **asayer-cli:**
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.
This script will help to manage asayer applications. Basic opeations covered are
We hope your cluster has provision to create a [service type](https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer) `LoadBalancer` for exposing OpenReplay on the internet.
```bash
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,
- 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:
```bash
cd helm && asayer-cli -h
cd helm && openreplay-cli -h
```