cyrildewit / laravel-accommodations Goto Github PK

Two increase the security of the platform, it might be usefule to have the ability to configure Two Factor authentication for your account.

The implementation needs to be generic and flexible, so it can be used inside all of the portals in different ways.

To do

• $room->isAvailableForPeriod(DateTime $start, DateTime $end);
• $room->isAvailableForDate(DateTime $date);
• $room->whereAvailableForPeriod(DateTime $start, DateTime $end);
• $room->whereAvailableForDate(DateTime $date)

• Routes for front
• Routes for portal
• Routes for management

Front routes

• / - Homepage
  • This page will contain the search form
• /search - Search results
  • This page will contain the search results
  • Maybe /d instead of /search (discover)
• /{listing-type}/{area-slug}/{listing-slug} - Listing page
  • This page will contain a listing

Secure routes

Domain: secure.laravel-accommodations.test

• /
  • This page contains the main overview (also known as a dashboard)
• /reservations
  • This page lists all reservations
• /reservation/{id}
  • Shows a reservation details
• /reviews
  • This page lists all given reviews
• /settings
  • This page contains all the configurable settings

Portal routes

Management routes

• /dashboard - Dashboard
• /users - Users
• /listings - Listings
• /bookings - Bookings

• Listing reviews
• Share listing on listing page
• A listing should have a gallery
• Show map of listing's location
• Listing facilities
• Listing house rules
• Localization
  • feature to change the locale, determine locale from the user agent
  • Store user locale in the users table

Overview

Roles summary

• Super Admin (super-admin)
• Manager (manager)
• Member (member)

Roles

Super Admin

This role has pretty obviously permission to all available permissions. This will be done using the Gate::before() method.

Member

This role will be attached to registered users. It gives the user access to user specific areas

Technical

Conventions

Decide:
// edit, delete, publish, unpublish
// browse, read, edit, add, delete

Right now, it's not easy to add new features because we can't test it out in the browser. Creating a simple UI allows us to create the authentication forms which enables us to log in directly in the browser.

Create authentication views for all environments. They don't have to be polished and have a great design. As long as they let you login, register, reset password and verify a user, it's good enough for v0.1.0

Right now it uses the address model, but this table contains to much unrelated junk like personal information. Maybe a locations table that stores all kind of information: lat, long, address, postcode ... without user binded data.

The specification for this experiment is as follows:

This is implementation will be created for the management portal only. Manual registering isn't possible, so we only need to take extra steps when employees are logging in or when users need to re-authenticate.

Pre thoughts

1. We need a middleware to protect pages where you need to be authenticated (not the same as authorized). Little bit the same as the Authenticated middleware. I think it's okey to keep the middleware seperated for easy removal and abstracter code.
2. We need a page to setup this application in someone's Authenticator app, so they're able to get login tokes
3. We need a page to check for a correct login token, so the user is able to view the protected pages

To do

• Install pragmarx/google2fa
• [x]

Tasks

Secure

• Finish the login, register, and password reset functionality
• Add a user profile picture functionality
• Design the initial version of the secure environment (navigation)

Management

• Build the login, register, and password reset functionality
• Add a user profile picture functionality
• Create an empty dashboard page
• Build the initial version of the listings index page