rwarbelow

This is random text

More

• than
• before

• Howdy

rwarbelow

Use a Schema Designer to create schemas for the following problems:

1. City Library System

• a user can check out books
• books have one or more authors
• books belong to a library branch
• a book can be reserved by a user

2. Movie Showtimes

• a movie has many showtimes at various theaters

rwarbelow

1. Write a program that can convert Arabic numbers 1-3000 to Roman numerals. For example:

converter = RomanConverter.new
converter.to_roman(6)
=> "VI"

converter.to_roman(14)
=> "XIV"

rwarbelow

1. Sign in to GitHub and go to https://github.com/new
2. Type in the name of your project for repository name
3. Select the checkmark for "Initialize this repository with a README"
4. Click "Create Repository"
5. Click the button "Create new file"
6. In the box that says "Name your file..." enter index.html
7. Paste your HTML into the large text box area
8. Click "Commit new file"
9. Click "Create new file" again
10. In the box that says "Name your file..." enter styles.css (or whatever you called your stylesheet file)

rwarbelow

https://web.archive.org/web/20150221125906/http://www.sewingandembroiderywarehouse.com/embtrb.htm

https://www.facebook.com/uniladmag/videos/5192506594105691/

http://www.cakewrecks.com/home/2009/5/4/happy-falker-satherhood.html

rwarbelow

Use what you know about Ruby, Rails, MVC, sessions, etc. to create the following pieces of functionality:

1. A user who already exists in the database can log in using a username/password combination that they enter in a form. They should know that they are logged in because something like "Welcome, Rachel!" should appear at the top of every page they visit.

2. A user who already exists in the database and is already logged in should be able to log out. They should know that they are logged out because their welcome message will no longer appear at the top of every page they visit.

3. Users should have many jobs, and a job should belong to a user. Therefore, when a user visits any jobs listing, they should only see jobs associated with them. They should not be able to see, edit, or delete any jobs that are not associated with their account.

4. A user who does not exist in the database should be able to create an account through a form that gathers any necessary user information. Once they create an a

rwarbelow

Part I: User Creation

1. add route for new_user_path
2. create a UsersController with new action
3. create new.html.erb
4. generate user model with password_digest string field
5. uncomment gem 'bcrypt' in Gemfile and add has_secure_password in User model
6. add create action in UsersController
7. implement logic for creating a user
8. set session[:user_id] in create action

rwarbelow

Right now, your Job Tracker app is available to use by anyone. Wouldn't it be nice if we could make it so that only logged-in users could access the site?

Today, you'll attempt to implement authentication in your Job Tracker app. This challenge is not meant to give you step-by-step instructions for implementing authentication. Instead, you'll be prompted with places to start, things to cosider, and resources to reference, but you'll want to consider the implications of your choices along the way.

Before you start, read this article which talks about the difference between authentication and authorization. We'll focus most of this challenge on authentication, although you will see bits of authorization.

The purpose of the challenge is to figure out the moving pieces of authentication, not to TDD the authentication process. Therefore, don't worry about writing tests.

As you go through this challenge, push to try to get as many pieces figu

rwarbelow

Homework

1. Using a Flash

Implement a flash[:notice] in the ToolsController #create action for when you successfully create a tool. Extension: Modify your #create action to conditionally create a tool depending on whether or not a name is provided. Then create a flash[:error] that holds @tool.errors.full_messages.join(", "). Use a dynamic content generator to display the flash notice. Take a look at 20:33 in the Sessions, Cookies, and Flashes video for a refresher on how to do this.

2. Storing Most Recent Tool in the Session

• Store the id of the last tool added to ToolChest in the session with a key of :most_recent_tool_id.
• Add a method to your ApplicationController called most_recent_tool that loads the most recent tool using :most_recent_tool_id stored in the session. (Hint: use Tool.find... and make sure it doesn't break if there are no tools in the database!)

rwarbelow

require 'mail'

mail = Mail.new do
  from 'rachelwarbelow@gmail.com'
  to 'rachel@turing.io'
  subject 'Hello!'
  body 'This is an email that was sent using Ruby.'
end

mail.delivery_method :sendmail