crescentrose / chat-log Goto Github PK

This should be fairly easy after #11

• SteamId class has a ::from_vanity class method

• navigation should make sense
• pages should have help text and hints where necessary
• notifications/alerts should look better

• Control root user via environment variables
• Allow root user to create roles and assign permissions to roles
• Allow root user and users with user management permission to assign roles to users
• Compute permissions based on the roles

What it says.

You should not be able to edit the Administrator and Everyone role names, because some parts of the system rely on that role being there with that name.

• fetch the current server status and player list
• fetch basic server performance stats (?)

• implement a "common messages" list with customizable words, with defaults:

gg
ggwp
gg wp
lol
scramble
vscramble
!vscramble
votescramble
nominate
!nominate
rtv
( ͡° ͜ʖ ͡°)
***UBERED***
ok
hi

• common messages get "collapsed" (e.g. one line saying X common messages) in the messages list

OR (easier):

• toggle to display all vs. filtered messages in the message list

Right now we have a User::TRUSTED_USERS constant which contains the array of user IDs that are "trusted" and whose IPs won't be logged. This should be a permission on a role instead.

• add new permission
• add a way to add users into the system without them having to log in (limited to root users for now)
• use steam API to fetch username, avatar and verify steam id
• add the logic to fetch users with that permission to the log file processing service and pass the array of users to the ConnectionParserService constructor so that we don't get a bunch of database calls for every single connect/disconnect log entry line
• delete the TRUSTED_USERS variable

This will also resolve the issue of people having to be log in once first before being granted access that they need.

https://github.com/marketplace/actions/dokku-deploy-action

• add a "flag" to the message
• when parsing, use a common list of naughty words that will trigger an auto-flag

• add, update and delete servers
• assign friendly names and rcon password
• assign ssh details (?)

Come up with a better way to represent the server status with regards to log sync and rcon sync.

• monitor processed and new log files through an ssh connection
• download said log file when it's not seen yet

We can use the free version of Sentry to collect errors.