MERN skeleton

[daisycrego]

• Express backend serving a SPA react app, connected to a mongo cloud database instance (Mongo Atlas).
• At its core, the app will collect and display Events from the FUB on an admin screen, and will store those events, including whether or not they have been addressed, in the DB.
• This is a todo tool where the data is currently coming from events/ in the FUB API.
• The working skeleton should be able to collect API data, store it in the db, and display that to the end user. Waiting on Dan for specifics on the UI and more decisions to be made on the functionality. BUT, we know that for sure the React frontend is fetching data, storing it in the db by communicating with the backend, and displaying that data with some action buttons to the user.

[daisycrego]

package.json

• "scripts"->dev/start runs index.html

• index.html similar to https://github.com/daisycrego/react/blob/master/notedly/web/src/index.html

• index.html runs the React app, App.js

• So do we need an express app? https://stackoverflow.com/questions/15718649/how-to-publish-a-website-made-by-node-js-to-github-pages

[daisycrego]

Take a look at this code: https://github.com/shamahoque/mern-skeleton

[daisycrego]

Here is a react template I wrote based on the JavaScript Everywhere textbook: https://github.com/daisycrego/react/tree/master/react/reactJS/reactTemplate

[daisycrego]

• [ ] Refactor the builderbook code

  • has a ton of useful stuff, but it's Next.js and we don't really need that right now, we can have a SPA.
  • We just need that withAuth HOC, and sign in with gmail would already be in place, basic schemas are there to build off of, there's a lot to start with but not a bunch of crap, good enough to go.
  • So, the plan is to remove the Next.js from notedly,
  • set up a basic SPA which is protected by authentication, with Google sign in, and
  • display on the home page the contents of the Events model in mongodb. That events model is going to be populated in 2 ways:
    • User clicks "Sync" button and queries the FUB /events endpoint, updates the db with any new events
    • Scheduled runs to query the FUB/events endpoint, updated the db with any new events

• [ ] Create an API endpoint, /sync-events, to query the FUB /events endpoint and update the database, then return a list of the updated events for the UI to display.

  • This API endpoint can be then triggered either by the scheduled events of sync button, whichever is needed.
  • Note: Alternatively, we could attach a fetch call to the FUB API directly from the click button on the UI. But, we won't have access to the database, so we really can't do all the work we need to there, yes better to make the /sync-events endpoint.

[daisycrego]

Used a mern skeleton from here, I could understand all of the code so that was a great sign, and it used all of the technologies I wanted to use: webpack, node.js, mongoose, babel, react, express, everything.

Connected to a mongodb atlas instance, under a new db collection, jbgadmin, and created some schemas/models for the User and Event objects.

Working on an events/sync endpoint to call the FUB API, retrieve events, compare those to the existing events, etc. Need to make some decisions about how I'll properly use offset to retrieve all the events.