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

[Bug]: Quickstart guide not working for local setup #3508

Open
sujal03 opened this issue Nov 28, 2024 · 2 comments
Open

[Bug]: Quickstart guide not working for local setup #3508

sujal03 opened this issue Nov 28, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@sujal03
Copy link

sujal03 commented Nov 28, 2024

What happened?

Hi,
I tried running Quivr locally by following the Quickstart guide, but it didn’t work as expected. Below are the details of the issue:

Steps Followed:
[List the specific steps you took from the guide]
Error/Issue:
[Mention the error message or issue encountered. If possible, include screenshots or logs.]
Environment Details:
OS: [Your OS and version]
Node.js Version: [Your version, if applicable]
Any other relevant configurations.
Let me know if there are additional steps or configurations I need to follow. Thanks!

Relevant log output

No response

Twitter / LinkedIn details

No response

@sujal03 sujal03 added the bug Something isn't working label Nov 28, 2024
Copy link

linear bot commented Nov 28, 2024

Copy link

dosubot bot commented Nov 28, 2024

Hey @sujal03,

I'm here to help you with any bugs, questions, or contributions while you wait for a human maintainer. Let's tackle this together!

I found a similar open issue where the suggested solution was to update the repository and rerun the setup. You can try running git pull and then docker compose up again. If you're using your own VPS, you might want to follow the deployment procedure outlined here: Digital Ocean Deployment Guide [1].

Additionally, there are a couple of closed issues that might be relevant. One suggests that the problem could be related to the startup order of services in Docker Compose. You might need to ensure that services are fully ready before others try to connect to them. Another issue was resolved by converting a script file to Unix format using dos2unix backend/core/scripts/start.sh and then restarting Docker Compose [2][3].

To continue talking to Dosu, mention @dosu.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant