Added information about providing own database and Firebase after grading is over into readme#125
Merged
Merged
Conversation
…ester is over into readme
trappaly
reviewed
May 12, 2025
|
|
||
| **Note:** | ||
| After Spring 2025 grades are released by Grinnell College, the availability of database credentials used for our development cannot be guaranteed. | ||
| The availability of Firebase credentials cannot be guaranteed as well. |
Collaborator
There was a problem hiding this comment.
notes to usersabout database credentials and firebase credentials
trappaly
reviewed
May 12, 2025
|
|
||
| How to set up the database will depend on whether the database services used for our development are still available: | ||
| - Before Spring 2025 grades are released, you may ask a team member for credentials. | ||
| - This way, graders may use the team's credentials for grading purposes. |
Collaborator
There was a problem hiding this comment.
Information on how to set up the database
trappaly
reviewed
May 12, 2025
|
|
||
| ### Installing Prisma Client (Tool Used to Access Our Database Neon) | ||
| ##### Getting Onboard with Neon (Our Database) | ||
| 1. Optional: Ask Madel to add you to the StressLess Neon database. (Optional: For testing, you can use ThunderClient, which you can easily download on VSCode under Extensions.) |
Collaborator
There was a problem hiding this comment.
Instructions on how to set up Neon, our database
trappaly
reviewed
May 12, 2025
|
|
||
| For more information on **Prisma**, check out [Prisma Guide](./docs/dev%20docs/database/Prisma.md) | ||
| For more information on how to use **Prisma** after initial setup, check out [Prisma Guide](./docs/dev%20docs/database/Prisma.md) | ||
|
|
Collaborator
There was a problem hiding this comment.
Information after grades are released
trappaly
reviewed
May 12, 2025
| ## Acknowledgments | ||
|
|
||
| We would like to thank Professor Leah Perlmutter and our class mentor Elliot Swaim for their guidance and support throughout this project. | ||
| We would like to thank all of our stakeholders who gave us useful feedback to help us improve our app. We want to thank [this YouTube tutorial](https://youtu.be/VrC5XhjW6W0?si=_ibhdo7doCMXNtB3) for helping us implement our frontend calendar. |
Collaborator
There was a problem hiding this comment.
Acknowledgements to everyone who helped us
trappaly
reviewed
May 12, 2025
Collaborator
trappaly
left a comment
trappaly
left a comment
There was a problem hiding this comment.
Looks good Tim! Thank you for the very detailed descriptions for users to set up and continue the project.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.