Skip to content

Latest commit

 

History

History
117 lines (80 loc) · 5.09 KB

meetups-in-space-1-migrations.md

File metadata and controls

117 lines (80 loc) · 5.09 KB
Raw

When we noticed that Meetup.com didn't allow users to create meetups that take place in space, we knew we had our new business plan. Our goal is to disrupt the meetup space and bring synergy to meetup groups and their members throughout the entire universe. Why limit our market to just Earth?

Learning Objectives

  • Effectively structure data to minimize duplication.
  • Model connections between information using one-to-many and many-to-many relationships.

Instructions

Over the next three days, you'll be building a website similar to Meetup.com that allows users to sign up, join existing meetings, and even create their own meetup. This will be broken down into three parts - Day 1 is described below. To start, read through the following user stories to learn about what the finished app should do.

The application should satisfy the following user stories:

As a user
I want to view the details of a meetup
So that I can learn more about its purpose

Acceptance Criteria:

  • I should see the name of the meetup.
  • I should see a description of the meetup.
  • I should see where the meetup is located.
As a user
I want to view a list of all available meetups
So that I can get together with people with similar interests

Acceptance Criteria:

  • Meetups should be listed alphabetically.
  • Each meetup listed should link me to the show page for that meetup.
As a user
I want to create a meetup
So that I can gather a group of people to discuss a given topic

Acceptance Criteria:

  • I must be signed in.
  • I must supply a name.
  • I must supply a location.
  • I must supply a description.
  • I should be brought to the details page for the meetup after I create it.
  • I should see a message that lets me know that I have created a meetup successfully.
As a user
I want to join a meetup
So that I can talk to other members of the meetup

Acceptance Criteria:

  • I must be signed in.
  • From a meetups detail page, I should click a button to join the meetup.
  • I should see a message that tells let's me know when I have successfully joined a meetup.

User Authentication

The authentication system has already been implemented using the OAuth standard with GitHub's authentication service. You'll need to register your development app with GitHub and provide your own application keys using the following instructions:

  1. Go to your application settings page on GitHub and register a new application (the name of the application doesn't matter).
  2. Set your "Homepage URL" to http://localhost:4567/.
  3. Set your "Authorization Callback URL" to http://localhost:4567/auth/github/callback.
  4. In the .env file fill in the values for GITHUB_KEY and GITHUB_SECRET that are provided on the GitHub settings page for your application.

Setting Up the Database

If you look in config/database.yml you can find the details of how to connect to your PostgreSQL database. In db/migrate you'll see that there is a migration that has already been written to create the users table.

Run the following commands to create and migrate your database:

# Install all the dependencies for the app
$ bundle install

# Create the database
$ rake db:create

# Run all the migrations to get our schema up to date
$ rake db:migrate

# Start the application
$ ruby app.rb

At this point you can visit http://localhost:4567 to view the application.

Resources

Day 1 Assignment

A good first step before approaching any problem is to go through the code you've been given to start with. Look through what has been already set up in the files provided here (mostly user authentication things), and try to get a general understanding of what you have to work with.

Today will be focused on designing and setting up the schema for the app. Once you're done looking through the existing code, your first step should be to plan out what tables you need, and what columns each one should have.

Next, use a tool like draw.io to create an ER diagram for your schema.

When your ER diagram is finished, create the migrations required to set up your database! Make sure to try rolling back each migration (rake db:rollback) to make sure that works, before you consider it finished.

When you finish these steps, start setting yourself up for future work on the above user stories. Don't worry yet about retrieving information from the database - that'll happen tomorrow - but you can get ready for that step by setting up the pages you'll need, and your paths in app.rb.