Add documentation for running the application without external services

[mcruzdev]

Hi @mcruzdev , I set the OPENAI_API_KEY and enabled quarkus.sqs.devservices.enabled=true as suggested. However, when running the app, it still fails with missing config errors for whatsapp.messages-processed.queue-url and whatsapp.incoming-messages.queue-url. Should these be explicitly set, or should DevServices handle them automatically?

Hi @kotlalokeshwari098, I think we need to create it manually using an script, take a look here https://docs.quarkiverse.io/quarkus-amazon-services/dev/dev-services.html#quarkus-amazon_quarkus-aws-devservices-localstack-init-scripts-folder

Again, we need to update the documentation for contributors that do not want to use a real service, I will create an issue for it, the same thing for OpenAI, we can use ollama locally.

Originally posted by @mcruzdev in #125

[mcruzdev]

Probably will be necessary to configure the application.

[Gabrielx47]

Good night! @mcruzdev I want to work in this issue.

[Gabrielx47]

@mcruzdev @jonaellemos @matheusandre1 Good morning! I'm getting this error in the whatsapp application. It's related to the whatsapp-web.js package. Has anyone else with this problem?

[matheusandre1]

@Gabrielx47 Hello, hm...
The project you mentioned hasn't had any recent code changes, only a code style adjustment.

I believe it's some kind of internal package version issue. If you followed the README guidelines, you can open a pull request about it and update the package with npm update whatsapp-web.js and check if it works correctly.

[mcruzdev]

@Gabrielx47 as we are using a library that looks the whatsapp web HTML and CSS. Everytime that facebook changes the whatsapp is necessary a new release from whatsapp-web.js, please do what @matheusandre1 said, update the whatsapp-web.js, if works, send a pr with the changes.

[Gabrielx47]

@matheusandre1 @mcruzdev Hello! I updated the whatsapp-web.js to the latest version, but it didn't work. I found a post talking about this: wwebjs/whatsapp-web.js#5718.

[matheusandre1]

@Gabrielx47 Check which version of RemotePath is related to the issue and, if possible, change it to make it permanent for now.

[Gabrielx47]

@matheusandre1 The version of the whatsapp-web.js in remote repository is 1.34.2.

[matheusandre1]

@Gabrielx47, Great, the last version that was working, right?

[Gabrielx47]

@Gabrielx47, Great, the last version that was working, right?

@matheusandre1 Yes. But it doesn't work anymore.

[matheusandre1]

@Gabrielx47 Okay, send a pull request about that, with a screenshot or something similar, and Matheus will review the pull request.

[Gabrielx47]

@Gabrielx47 Okay, send a pull request about that, with a screenshot or something similar, and Matheus will review the pull request.

@matheusandre1 Okay. Without whatsapp app, i can't test if Ollama is working correctly.