rjp2525 / falconfrag Goto Github PK

Will be switching over to use Angular instead of PHP/Blade, to make API requests more secure we'll use JSON Web Tokens and CSRF tokens for form submissions.

Provide more detailed analytics about the usage of everything with statsd

In order for a customer to review a specific product, they must meet the criteria:

• Be a paying subscriber of that particular service for a minimum of (3+?) months
• Account must have no unauthorized chargebacks
• Account must have no outstanding balances owed for services provided by Falcon Frag
• Account must be free of any flags added by either the system or a staff member

Customers who meet this criteria will also have a "Helpful" of "Not Helpful" button available to them on other reviews for that product. An autonomous analysis method will be added to add flags to accounts that appear to be abusing this system (beginning with captcha requirements, then continued abuse will disable the review helpfulness rating feature for that account).

User.php line 19

lucadegasperi/oauth2-server-laravel is abandoned.

https://laravel.com/docs/5.3/upgrade#upgrade-5.3.0

A somewhat random idea, but it'd be nice to have excerpts of log files when notifying of a service error in the actual email itself.

Sub-accounts will allow primary clients to create separate accounts with owner-limited permissions to their selected products/services. These accounts may also submit tickets on behalf of the service they have access to, and the primary account owner will also receive an email with ticket information.

I'll have to come up with a separate system to handle it since our existing permission system lacks the necessary components.

We need to start implementing some unit tests for Travis CI to check. Assert the assertions!

Tracking changes to fields updated will not only provide an added layer of security for user data, but will also prevent fraudulent transactions that may result in a fake user data change.

Implement a feature that automatically backs up the database at least once daily and the site at least once weekly to at least one offsite cloud provider (ie AWS).

Permission based routing along with dynamic permissions that can be assigned to roles for much more flexible staff positions

When a response is unauthorized due to not being logged in, a modal should appear alerting the user they need to login again. If the user previously logged in is not permitted to access any administrative API endpoints, return a 404 response instead.

The Auditable class extension is redundant, needs to be removed soon.

I'll be creating a separate directory for the backend programs that will be run on Falcon Frag servers, as well as the daemon services associated with the products offered. Will probably not create a separate repository for them just to make it a little easier, but if it causes the languages to off balance as a result of long daemon code then I'll create a separate private repository for all daemon software.

Low priority/future implementation planned.

It's obsolete, the only good thing about it was not having a million sub directories when a dependency required another dependency that was already installed. Node/npm has since fixed this and there is no use for Bower anymore.

https://bosnadev.com/2015/03/07/using-repository-pattern-in-laravel-5/

Falcon Frag is currently on Laravel 5.0 with a limited number of things completed, so we'll want to upgrade sooner rather than later. Will most likely be completed tomorrow.