-
Notifications
You must be signed in to change notification settings - Fork 112
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
Docs/improve installation instructions #357
Docs/improve installation instructions #357
Conversation
🎉 Thank you for your contribution! Your pull request has been submitted successfully. A maintainer from team will review it as soon as possible. We appreciate your support in making Dataverse better. |
✅ Deploy Preview for multiverse-dataverse ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉 Thank you for your contribution! Your pull request has been submitted successfully. A maintainer from Dataverse
will review it as soon as possible. We appreciate your support in making this project better.
I'm closing this PR request since few conflicts needs to be resolved first. |
@Rucha-Ambaliya many changes have been made in the main repository after you forked it, that's why there were many merge conflicts. You can run |
I thought so too. Since the conflicts were manageable, I went ahead and resolved them on my end. I've created another PR now—hopefully, this works smoothly. Thank you for your guidance! 😊 |
Description
Updated Installation Instructions:
Related Issue
Fixes #356
Type of change
Checklist
Additional Thoughts:
I’ve tried to keep the instructions as simple and structured as possible. Please let me know if there’s anything that can be improved further or if something is missing.
If I remember correctly, the position of main.py has changed, which is causing conflicts with imported file paths. Should I create an issue to track this bug? Additionally, there are some packages that need to be added to requirements.txt I would like to address those bugs as well!