Skip to content

freecodecampBarrie/rubberduck

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

75 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

The Rubberduck Project

We're going to make a web app that re-creates the Rubber Duck Debugging experience.

Here's the wireframe of what we're aiming for MVP.

Here's our Trello Board. We're using Github's Project tab, which is a great kanban tool available to us.

We also have a Github Team for approving PRs and Merges, also ask during Zoom call to become a member.

We'll also be referencing this tutorial to setup the MERN stack.

@paulywill tested and showcased the tutorial's demo.

Goals within 2 OR 3 hour meetups:

  • Discuss workflow with group
  • Setup ideal environment / Trello / IDE / Sharing Etc.
  • working MERN stack
    • creating a database
    • getting all the CRUD parts working
    • React frontend that tackles close to wireframe/prototype
  • Host working MVP on Heroku/Netify/whereever
  • Add some CI/CD for fun?
  • Redirect with newly purchased Google domain quackback.dev
  • Find out how effective Zoom + hackathon can really be VS Code vs. Repl.it vs. Codesandbox

Requirements

You are going to need the following installed on your machine:

Getting Started

  1. fork project to your own Github account

  2. Clone your fork to your computer (aka "local machine"):

    git clone https://github.com/[your_username]/rubberduck.git

  3. Set up remotes to work with team

    git remote add upstream https://github.com/freecodecampbarrie/rubberduck.git

    You should see some similar after entering: git remote --v

     origin  https://github.com/[userid]/rubberduck.git (fetch)
     origin  https://github.com/[userid]/rubberduck.git (push)
     upstream        https://github.com/freecodecampBarrie/rubberduck.git (fetch)
     upstream        https://github.com/freecodecampBarrie/rubberduck.git (push)
    
  4. Install node packages:

    cd backend

    npm install

  5. Create MongoDB, we're using an online service (free tier) MongoDB Atlas. If you want the same one we're using just ask one of us for the secret credentials (just not @paulywill's credit card @T357A!!!)

  6. Once the MongoDB is setup you need to make to a .env file in the backend directory. You can reference env.sample for the basic setup to connect to the MongoDB Atlas database we're using.


Meetup V.5 - May 28, 2021

We covered a lot of ground as far as what we're trying to create and the Github workflow.

Even created a database cluster and able to connect. @paulywill struggled with connecting a new cluster (as described in #1), so we decided to use one that was already created previously and connect to that one.

Although did not get as far as ambitions hoped for, we did get a good footing for next month's meeting.

In the mean, keep pushing for PRs and merging changes you think are appropriate. Do not worry about breaking anything, that's the point.

Will update the minutes in our meetings repo.


Meetup V.6 - June 25, 2021

We'll continue on.

It's there's any work covered between then (hopefully working CRUD) we'll regroup and discuss what the next Sprint will be.


HOT TIP: To open links in a new tab users can just do a CTRL+click (on Windows and Linux) or CMD+click (on MacOS) on the link

HOT TIP #2: Have snacks and beverages near by.