CHIPS 5.3: Rails Intro
Add real features to RottenPotatoes: sorting and filtering the movie list, the Rails way. This is part of Module 5.
CHIPS 5.3 is an individual assignment — unlike CHIPS 4.8, you work on it and submit it on your own.
Goals
- Use ActiveRecord queries to sort and filter records in response to user choices.
- Preserve user interface state across requests using
session, and follow RESTful redirection idioms. - DRY out views and controllers using partials and filters.
- Deploy your enhanced app.
What you’ll do
You’ll extend the movie listing so users can sort by title or release date and filter by rating — with the twist that the app must remember each user’s settings. This is the classic “Rails Intro” assignment: small in code, rich in Rails idioms.
Before you start
Watch Module 5 §5.1–5.2 and read the matching textbook sections. You’ll need the working deployment setup from CHIPS 4.8.
Logistics
- Getting the code: see Getting the Code below — you clone the public starter repo and push it to a private repo of your own.
- Autograding: submit to Gradescope; you may submit as many times as you like before the deadline. The autograder is a way for you to check your work and your understanding. Run the tests locally first — see Running Code and Tests.
- Deployment: put the URL of your deployed app in
rottenpotatoes-url.txtbefore you submit. - Extensions: everyone automatically gets a 2-day no-penalty extension; see the extension policy.
- Collaboration: this CHIPS is individual — you may discuss high-level approaches with anyone, but write and submit your own code. Sharing code is academic misconduct. See the AI Use Policy below before using AI tools.
AI Use Policy
This assignment follows the course AI Policy, which will be published on this site before it is needed. Until then, the rule from the Syllabus applies: you must be able to explain everything you submit.
Getting the Code
Public starter repo: saasbook/hw-rails-intro —
https://github.com/saasbook/hw-rails-intro
GitHub makes it challenging to have a private fork of a public repository. These steps allow you to create a private space for you own work but still update from the starter code.
Clone the starter repo, then use gh
(see Local Development)
to create a private copy under your own GitHub account and
push the code to it. Replace YOUR_GITHUB_USERNAME with your
GitHub username:
git clone https://github.com/saasbook/hw-rails-intro.git
cd hw-rails-intro
git remote rename origin upstream
gh repo create YOUR_GITHUB_USERNAME/hw-rails-intro --private --source=. --remote=origin --push
git remote set-url --push upstream DISABLED
After this, origin is your private repo and upstream
is the public starter repo. The last command disables pushing to
upstream, so git push always goes to your own
copy — never to the public starter repo.
Keeping your repo up to date
Your private repo is a snapshot: it does not follow the starter
repo. If we fix or add something in saasbook/hw-rails-intro
after you copy it, you have to pull those changes in yourself. The
upstream remote you set up above is how you do that:
git fetch upstream
git fetch only downloads — it changes nothing in your working
copy. Review what you are about to take before merging it:
git diff --name-only HEAD upstream/main # just the names of the files that differ
git diff --stat HEAD upstream/main # the same list, plus how much changed in each
git diff HEAD upstream/main -- spec # the actual changes, limited to one file or directoryThen merge the upstream changes into your branch and push them to your private repo:
git merge upstream/main
git push origin main
If you and we edited the same lines, git stops and reports a conflict: open
each file it lists, keep the correct combination of both sides, delete the
<<<<<<< / ======= /
>>>>>>> markers, then git add
those files and git commit. Ask on Ed if a merge leaves you
stuck — don't start over and lose your work.
These commands assume the starter repo's default branch is main.
If git branch -r shows upstream/master instead, use
that name in the commands above.
View this assignment on bCourses.
Running Code and Tests
Run everything below from the root of your clone (see Getting the Code). If Ruby isn't installed yet, work through Local Development first.
Install the dependencies
bundle install
Run this once after cloning, and again whenever the Gemfile
changes. Prefix the commands below with bundle exec so you run
the same gem versions the autograder does.
Boot the project
Create the database (once, and after any new migration), then start the Rails server:
bin/rails db:migrate
bin/rails serverThe app is then at http://localhost:3000; Control-C stops the server. To try one thing without clicking through the UI, use the console, which loads your app and its models:
bin/rails consoleRun the tests
Run the RSpec suite the way the Gradescope autograder will — get it green locally before you submit:
bundle exec rspec # the whole suite
bundle exec rspec spec/YOUR_FILE_spec.rb # one spec file
bundle exec rspec spec/YOUR_FILE_spec.rb:42 # one example, by line number
bundle exec rspec --format documentation # every example's descriptionEach failure prints the file and line of the failing example along with what it expected — start there rather than at the top of the output.