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

🏖 MongoDB Setup #23

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

🏖 MongoDB Setup #23

wants to merge 1 commit into from

Conversation

josh-byster
Copy link
Contributor

@josh-byster josh-byster commented Apr 17, 2020

Fixes #8, this PR sets up all the MongoDB stuff necessary to run both locally and on Now. I will send the .env file privately with the database connection, which can go in /api/.env. However, this PR allows us to also test changes on production with Now, since it's hooked up to the database as well. In other words the Now deployment should be exactly like if you were testing it locally.

This uses MongoEngine, which has some awesome documentation and support.

You can see this DB connection tested out here:
https://uiuc-covalence-org-git-jb-mongo-setup.covalence.now.sh/api/

@vercel
Copy link

vercel bot commented Apr 17, 2020

This pull request is being automatically deployed with ZEIT Now (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://zeit.co/covalence/uiuc-covalence-org/l856s8l1g
✅ Preview: https://uiuc-covalence-org-git-jb-mongo-setup.covalence.now.sh

@josh-byster josh-byster changed the title MongoDB Setup 🏖MongoDB Setup Apr 17, 2020
@josh-byster josh-byster changed the title 🏖MongoDB Setup 🏖 MongoDB Setup Apr 17, 2020
Copy link
Contributor

@kenetec kenetec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks amazing! Thanks for all your help 😄

Copy link
Contributor

@AngelaLuo49021 AngelaLuo49021 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good josh!

  • With the designs for the individual project page up, it seems like we're going to need subfields for the descriptions and some other data fields as well.
  • Maybe description can be separated out into problem, efforts, and how you can help? In addition, the design seems to indicate that we want to have the school/location where the project is taking place.
  • designs indicate that a couple of images will be used per project page. I don't have much experience in the best practices of storing images in databases or else where so let us know your thoughts!

Screen Shot 2020-04-17 at 2 09 24 PM

In addition, as of last night the co-directors of covalence just sent some more info about what they were looking for in the website which differs from the spec a little
Screen Shot 2020-04-17 at 2 13 24 PM

  • given this, I think having a field of "tags" : [] that can list how the project is categorized will definitely be needed for filtering.
  • sry if some of this is confusing, trying to set up a meeting very very soon so we can get everything cleared up ASAP
    Thanks and let me know your thoughts! 🤠

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

database: set up schema for projects
3 participants