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

Doc/readme update #16

Merged
merged 5 commits into from
Feb 12, 2025
Merged

Doc/readme update #16

merged 5 commits into from
Feb 12, 2025

Conversation

joyguptaa
Copy link
Contributor

@joyguptaa joyguptaa commented Feb 9, 2025

Date: 12 Feb 2024

Developer Name: Joy Gupta


Issue Ticket Number

NA

Description

Updated ReadME wrt to latest workflow

Documentation Updated?

  • Yes
  • No

Copy link
Member

@iamitprakash iamitprakash left a comment

Choose a reason for hiding this comment

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

don't need to run command to enable rabbitmq management UI

@joyguptaa
Copy link
Contributor Author

don't need to run command to enable rabbitmq management UI

It is already written in the docker-compose file. So to answer your question, no we do not need a separate command. can be handled with single docker compose command

ports:
- '5672:5672' # AMQP protocol
- '15672:15672' # Management UI (optional)

@iamitprakash
Copy link
Member

don't need to run command to enable rabbitmq management UI

It is already written in the docker-compose file. So to answer your question, no we do not need a separate command. can be handled with single docker compose command

ports:
- '5672:5672' # AMQP protocol
- '15672:15672' # Management UI (optional)

readme is all about running locally and look data into local system so please update here as well @joyguptaa

@joyguptaa
Copy link
Contributor Author

readme is all about running locally and look data into local system so please update here as well @joyguptaa

But its already there in the readme.

## Running Discord Message Broker
There are 2 ways of running Queue and Consumer,
- either you can setup both with docker if you are not working on consumer
- but in case if you are working on consumer and want hot reloading, go with running consumer manually
## Way 1: Running both RabbitMQ & Consumer using Docker
Set the following env var(s)
```
QUEUE_URL = "amqp://rabbitmq:5672"
DISCORD_SERVICE_URL = "http://host.docker.internal:<PORT>"
DISCORD_QUEUE = <ANY_NAME> #Default: "DISCORD_QUEUE"
```
Run the compose command:
```sh
docker-compose up --build
```
## Way 2: Running RabbitMQ with Docker & Consumer manually
### Running only RabbitMQ with Docker
```bash
docker compose -f 'docker-compose.yml' up -d --build 'rabbitmq'
```
> [!IMPORTANT]
> To check if the queue is running or not, visit `http://localhost:5672`
### Running Consumer Manually
Set the following env var(s)
```
QUEUE_URL = "amqp://localhost:5672"
DISCORD_QUEUE = <ANY_NAME> #Default: "DISCORD_QUEUE"
DISCORD_SERVICE_URL = "http://localhost:<PORT>"
```

@iamitprakash
Copy link
Member

readme is all about running locally and look data into local system so please update here as well @joyguptaa

But its already there in the readme.

## Running Discord Message Broker
There are 2 ways of running Queue and Consumer,
- either you can setup both with docker if you are not working on consumer
- but in case if you are working on consumer and want hot reloading, go with running consumer manually
## Way 1: Running both RabbitMQ & Consumer using Docker
Set the following env var(s)
```
QUEUE_URL = "amqp://rabbitmq:5672"
DISCORD_SERVICE_URL = "http://host.docker.internal:<PORT>"
DISCORD_QUEUE = <ANY_NAME> #Default: "DISCORD_QUEUE"
```
Run the compose command:
```sh
docker-compose up --build
```
## Way 2: Running RabbitMQ with Docker & Consumer manually
### Running only RabbitMQ with Docker
```bash
docker compose -f 'docker-compose.yml' up -d --build 'rabbitmq'
```
> [!IMPORTANT]
> To check if the queue is running or not, visit `http://localhost:5672`
### Running Consumer Manually
Set the following env var(s)
```
QUEUE_URL = "amqp://localhost:5672"
DISCORD_QUEUE = <ANY_NAME> #Default: "DISCORD_QUEUE"
DISCORD_SERVICE_URL = "http://localhost:<PORT>"
```

where is this step Management UI, read carefully before replaying @joyguptaa

@joyguptaa
Copy link
Contributor Author

where is this step Management UI, read carefully before replaying @joyguptaa

I hope I made the correct changes here.

Markdown Code

> [!IMPORTANT]
> To check if the queue is running or not, visit `http://localhost:15672`
### RabbitMQ UI
This is how the UI will look like once you open `http://localhost:15672`
<img width="1127" alt="Image" src="https://github.com/user-attachments/assets/81b67f52-c762-4773-b75d-26e82d558b36" />
> [!IMPORTANT]
> User "guest" as username and password

README Visuals

Screenshot 2025-02-13 at 12 56 17 AM

@iamitprakash iamitprakash merged commit 2c25acf into develop Feb 12, 2025
@iamitprakash iamitprakash deleted the doc/readme-update branch February 12, 2025 20:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants