Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ChaosCenter developer guide docs locally #282

Merged
merged 8 commits into from
Sep 19, 2024

Conversation

kwx4957
Copy link
Contributor

@kwx4957 kwx4957 commented Jul 31, 2024

What this PR does / why we need it:

  • Add sidebar and docs for developer Guide
  • Update current version docs for developer Guide

Currently, the development document has not been updated. It will not work if build development environment for the code according to the development document.

  1. There is no guide for Windows OS
  2. The version of mongoDB does not match with the version in helm
    • mongodb version 4 to 5
  3. It does not run because there are no environment variables such as GRPC_PORT and REST_PORT

Preview Link

image

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Special notes for your reviewer:

Checklist:

  • Fixes #
  • [v] Signed the commit for DCO to be passed
  • Labelled this PR & related issue with documentation tag

Copy link

vercel bot commented Jul 31, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
litmus-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 11, 2024 5:23am


## **Prerequisites**
:::note
This document is ietented to be implemented locally. Please do not use in dev or prod environmentss
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This document is ietented to be implemented locally. Please do not use in dev or prod environmentss
This document is intended to be implemented locally. Please do not use it in dev or prod environments.


## **Control Plane**
Backend components consist of three microservices
1. GraphQL-Server
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. GraphQL-Server
1. Backend server

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's fine to have graphql server since we have 2 backend servers

Copy link
Contributor Author

@kwx4957 kwx4957 Aug 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shoud we use graphql server for the name??
in docs using graphql

## **Control Plane**
Backend components consist of three microservices
1. GraphQL-Server
2. Authentication-Server
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
2. Authentication-Server
2. Authentication server

Comment on lines 48 to 87
Windows
```bash
# add hosts in hosts
notepad C:\Windows\System32\drivers\etc\hosts

# add the below line
127.0.0.1 m1 m2 m3
```

Linux/Mac
```bash
# add hosts in hosts
sudo vim /etc/hosts

# add the below line
127.0.0.1 m1 m2 m3
```


Step-3: Configure the mongoDB replica set

```bash
docker exec -it m1 mongo -port 27015

config={"_id":"rs0","members":[{"_id":0,"host":"m1:27015"},{"_id":1,"host":"m2:27016"},{"_id":2,"host":"m3:27017"}]}

rs.initiate(config)

db.getSiblingDB("admin").createUser({user:"admin",pwd:"1234",roles:[{role:"root",db:"admin"}]});
```
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should use Docusaurus tabs for individual infra types to show them. Please refactor in all the places.

@neelanjan00
Copy link
Member

CC: @Saranya-jena please review to validate the content.

@neelanjan00
Copy link
Member

@kwx4957 thanks for the PR, it looks good, please make the suggested changes.

export HUB_BRANCH_NAME=v2.0.x
export INFRA_DEPLOYMENTS="[\"app=chaos-exporter\", \"name=chaos-operator\", \"app=event-tracker\",\"app=workflow-controller\"]"
export INFRA_COMPATIBLE_VERSIONS='["0.2.0", "0.1.0","ci"]'
export DEFAULT_HUB_BRANCH_NAME=master
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have updated the envs in the wiki, can you update them here as well?

Copy link
Contributor Author

@kwx4957 kwx4957 Aug 9, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, sure. I'll update

@kwx4957
Copy link
Contributor Author

kwx4957 commented Aug 9, 2024

@neelanjan00 thanks for reviews, i will refactor and apply suggestions changes!!

@neelanjan00
Copy link
Member

@Saranya-jena just wondering if it is a good idea to keep developer docs in the same place as end-user docs? As per convention, it should be present in the GitHub repository readme itself.

@hrishavjha
Copy link
Member

@kwx4957, This is added in 3.9.1 versioned docs, can you also add this in all the later versions and into master as well so that it gets into every version in future?

@kwx4957
Copy link
Contributor Author

kwx4957 commented Aug 23, 2024

@hrishavjha yes, i can. i will keep updated on future versions

@Saranya-jena Saranya-jena merged commit ceb8a67 into litmuschaos:master Sep 19, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging this pull request may close these issues.

5 participants