hrothwell / shiritori Goto Github PK

More scripts will be needed for if/whenever the EBS volume is wiped from instance. These scripts will need to:

• yum update
• yum install -y ruby
• yum install wget
• Install CodeDeploy agent using wget
• chmod +x ./install
• ./install auto
• service codedeploy-agent start
• Install java 11 : amazon-linux-extras install java-openjdk11 might work, forget what I used on initial setup

Keep track of chat rooms that have more than one user currently subscribed to them

• Already being done for shiritori lobbies, something similar would probably be suitable for chat rooms
• however, this may not fit the "flow" that is currently existing
• Plus, everyone is already dropped into "lobby" to start. Will people really be jumping around too much?

Allow users to pick their preferred color for how their messages will show up.

• Some sort of color picker widget?
• send hex to server, validate on server
• hex is sent out as part of BasicMessage object
• parse client side, validate structure, add style to message span?

add all words to list of words and send out list to users each time a new word is played

• Client renders list and displays it somewhere on screen

while playing shiritori, it would be cool to have a box somewhere on screen that can contain images of the words that were played. However, finding an api to fetch images has been kind of hard since my usual go to options have changed how they work

setup SNS for when deploys fail to send out an email to subbed users (me)

adding links in app that point to github project, maybe an email/issues link, etc

Relates to keeping track of words

• if we start keeping track of words and not allowing repeats, we will need a way to "clear" the game words and start over basically

not everyone knows what Shiritori is, so could include a button/tooltip/something that contains some basic rules of the game

I have been seeing several unexpected errors in the logs in AWS. Some have some information (POST not supported, not sure what endpoint), others have no info. They are all falling into the /error handler, so add more logging there to try and gather info (target endpoint in particular could be helpful)

Right now the site is only accessible via HTTP, not HTTPS. Would be a good lesson on networking to figure out how to set this up I think

update the "Admin" user's chat color during games of Shiritori so that it is easier to differentiate

make simple nav button(s) such as "Home" to get back to main page