liback / qwsite Goto Github PK

• Add author field
• Try to bulk parse the map titles?

In rare cases map names can be the same as others. One example is battle.bsp in deathmatch-maps.zip from Quakerepo.net which is not the same map as battle.bsp ("Battle Zone") made by old schooler Quid.

Currently only two fields are used; "name" (battle) and "description" (Battle Zone).

Suggestion for new fields:
Name - Unique name that may include user defined separator
Example 1: Battle [by Quid]
Example 2: Battle [Battle Zone]

FileName - Name of the file (not required to be unique)
Battle

Description - Long name of map
Battle Zone

Guest users can't do anything currently (other than register) as they have no role attached to them. Should get a readonly kind of guest role automatically assigned under the hood.

See if table cells can be made scrollable sideways.

Start transforming this repository into a backend focused one by making it into a REST API.

Entities that should be reachable via standard REST API calls:

• Maps
• Users
• Roles
• Permissions (read only just to be able to list when creating/updating role?)
• Authentication using JSON Web Token (JWT)
• Make sure there are authorization checks in the controllers

Make a specific Profile action in the User controller that checks if the ID matches with currently logged in user. Need to check up the (best) way to do this with Laravel.

Add author field for maps.

Password reminder feature comes with Laravel authentication scaffold package but is not set up correctly nor tested.

Currently only a placeholder image is shown.

Thoughts:

• Should all images have a DB record or is it (fast/reliable/whatever) enough to just read file/folder names with a given syntax, iterating through the directories?

Currently all links (create/edit/delete etc) regardless of whether the user has access to the action that the button leads to or not. Should only be shown if user has access to feature.

Use Laravel intervention package.