scalableinternetservicesarchive / luber Goto Github PK

Every time a new user registers an account, send an email to the address with a special link that proves the user owns their email account.

Need 'make' (as in make & model)

Example: My car shouldn't have tags "no smoking" and "no smoking".

• Note: db seed file will need to not create duplicate tags when creating cars.

Add a signup form to allow new users to register an account.

pretty self-explanatory.

A not-logged-in visitor can only access:

• signup
• sitemap pages
• login
  • should NOT be able to get to any rental posts
• if not logged in and try to get otherwise, should redir to login / signup page.

Example: user deletes acct => his cars & RPs are also deleted

Need to style & reposition the notifications (flash hashes) that are shown when deleting / editing / creating things

As owner, when I "create rental post":

• should see list of cars, not car id
• date validation: end date after start date
• no renter
• no owner (i am the owner)
• price field validation: 2 dec pts max, display like $

See https://piazza.com/class/j789lo09yai5qx?cid=45

As a car owner, I can upload pictures of my car, in order for the renter to see it before fixing up a meeting.

A user can select a car to rent and somehow request to rent that car.

Stylize our page so it looks good.

Give users the ability to login/logout; with all security features like cookies.

Example: as user2, I shouldn't be able to see details of user1's car, even if I have his car's URL.

As a guest, I can view the available car-rental offers, in order to get an idea of what the site does.

As a site admin, I can delete fraudulent posts, in order to maintain users’ trust.

On the home page, there should be links to (1) view rental posts and (2) create a new rental post.

Allow users to reset their password by sending them an email with a link to a special password form for updating a new password.

As a car owner, I can deny renting out my car to a person if they do not seem trustworthy, in order to avoid risks.

As a car renter, I can see the contact information of car owner and preferred method of meeting, in order to meet the owner and collect the keys.

• rental post status (an integer)
  • avail, upcoming, in prog, completed, cancelled

Lets make a very basic car model first with fields we know we'll need for sure and then we'll add to it later on.

@Heronalps can you upload an image of the car model you took last Thursday?

As a car owner, I include the cost of my car in my posting.

While maybe not the best way, the easiest way I could think of doing this would to be to make a new "action" model, which basically contains a timestamp and a description. Everytime the user adds a rental post, edits a car, changes their profile, etc, an action object is created in the database.

For instance, say the user is adding a new car. When they click the "Create the car" button, not only does the info for the car get submitted and the car object created in the database, but a string is formed with its info as the action description and it is also submitted with the timestamp, something like "Added a new car: (Color) (Year) (Make) (Model) to my cars".

Thus the history section is a timestamped log of each of these actions, and when a user deletes something or it expires, it simply creates another audit log rather than requiring us to maintain some sort of relationship between past logs and everything else

Maybe as a button on the bottom right of their info section on the overview page of their profile?

Fold coverage reports as part of continuous integration to ensure that tests are checking most of the application logic.

For now we have username, password, and email in the user model. This issue is the discussion for what other details/fields should be part of the user model.

As a car owner, I can specify criteria like “non-smoking” and “no freeway driving” so that my renters treat my car the way I want.

As a car owner, I can see the location of my car through my renter’s phone’s location, to reassure me it’s in good hands.

As a car owner, I can see a map of where my car is, in order to reassure me it is safe.

"rails debug" (red banner at bottom) should only show if logged in as admin

As any user (even guest user), I can see static pages like FAQ, About, Contact, and Home, to get an idea of what Luber is all about.

As a car owner, I can upload a list of features that my car has, in order to help the renter in finding the best match.

It will make our URLs look better.

For example, if my username is "BobZ42" and I'm user ID 1, my account path should be:

/users/bobz42/overview

NOT

/users/1/overview

As a car owner, I can upload a list of features that my car has, in order to help the renter in finding the best match.

Make sure the project runs the same in production as it does in dev. This includes:

• Images should load
• Favicon should load
• Javascript components function properly
• Data is stored/deleted from the database correctly
• Any other issues that may arise

As a car owner, I receive notifications of my renter’s trip, and when my renter has returned the car, including statistics like the top speed the car attained, to reassure me the car was driven responsibly.

As a car owner, I can post the time and location when my car will be available, in order to rent it to other people.

As a car owner, I can see a schedule of who is renting my car, where they’ll pick it up, and when they’ll return it, in order to organize my rentals and stay in sync with my renters.

• username
• replace "name" with first name & last name
• city & state
• 'when last logged in'

If web browser goes to path that generates an error:

- if not logged in or non-admin user: DO NOT show rails debug screen. Show 404.
- if logged in as an admin: show rails debug screen

As a car renter who is reserving a car, I can use a nice map UI to see the location of the car, in order to plan my trip.

As a site admin, I can see a list of all users and rentals, and their states, so that I can help users who are experiencing problems with the site.

As a car-seeker, I can search for available car-rentals in my area, in order to get a car for the day.

As a car renter who bikes, I can filter out cards with a large trunk or roof attachments, in order to fit all my equipment.

As a car renter who is a parent, I can search for cars that have child seats, in order to assure safety of my children.

As a car owner, I can remove my car from the public listing

Once we figure out the basic fields in a user model (see issue #11) then we should make a webpage that allows users to update their profile.

... so we don't have to recreate the db each time.