Running the application without external services#221
Running the application without external services#221Gabrielx47 wants to merge 4 commits intomcruzdev:mainfrom
Conversation
mcruzdev
left a comment
There was a problem hiding this comment.
Thanks a lot for this pull request @Gabrielx47, it looks great and will help more people to try it locally!
I left few comments, could you update our documentation that talks how to run locally?
| <artifactId>quarkus-quinoa</artifactId> | ||
| <version>${quarkus-quinoa.version}</version> | ||
| </dependency> | ||
| <dependency> |
There was a problem hiding this comment.
Okay. Both are necessary, as one is used for local execution and the other for production execution.
| whatsapp.incoming-message.queue-url=${INCOMING_MESSAGE_FIFO_URL} | ||
| whatsapp.recognized-message.queue-url=${RECOGNIZED_MESSAGE_FIFO_URL} | ||
|
|
||
| %local.quarkus.http.auth.proactive=false |
There was a problem hiding this comment.
why we need this one?
This is necessary because, for the registration to be successful, without it the server returns a 401 error. I still don't understand why, since the SignUpResource class has the @PermitAll annotation. In theory, the server shouldn't deny the registration. From what I've researched, this happens due to Quarkus' proactive authentication.

There was a problem hiding this comment.
This error occurs because it's in a pull request that has already been fixed #195
There was a problem hiding this comment.
This error occurs because it's in a pull request that has already been fixed #195
Good morning, @matheusandre1! I did a merge between the main branch and my branch.
There was a problem hiding this comment.
Could you remove this file from changes?
Good morning, @mcruzdev! I'm happy to contribute and gain knowledge at the same time. I'll update the documentation. |
…s' of https://github.com/Gabrielx47/timeless into running-the-application-without-external-services (mcruzdev#150)
Sounds good friend! You are welcome :) |
I'm having trouble running the WhatsApp application:

I used
npm audit fix, but that didn't solve the problem.I'm also having problems with the

whatsapp-web.jspackage.This problem occurs when a message is sent and the bot attempts to read it. The current version of the
whatsapp-web.jspackage is1.34.2. However, even after updating to version1.34.4, the problem persists.