c-hive / ws-anywhere Goto Github PK

The related comment is available here.

This should make it explicit whether the periodic feature is in use.

One of the two button should always be disabled. This is enough feedback in this case, no need for ticks. But make sure that the button style only changes if the request was successful. By default the feature is stopped.

After all basic functionality is done, do a revision of the displayed text, instructions, etc.

It should include a script that automatically sets up heroku. E.g.

export HEROKU_APP=ws-anywhere

heroku apps:destroy --confirm $HEROKU_APP
heroku create $HEROKU_APP

heroku addons:create mongolab

heroku git:remote
git push heroku master

heroku ps:scale web=1

Let's fix this and also a few things to improve:

• feedback on start/stop - i know this was considered but looking at this error i think it's better with feedback
• if submit (or anything else) errors on the server side let's display Server error (similar to Invalid JSON format).

Add a conditional basic auth middleware to express.sj

If the ENV vars user AND password are set the admin should require based authentication based on these values. Otherwise not.

Document this feature in the readme.

Settings should be persisted to survive heroku restarts.

A button that disconnects all clients. Provide usual feedback.

Found some further improvements/issues regarding the periodic messages:

• clicking on the Submit button while the message sending is active doesn't affect its state - requires hitting the stop and start buttons once again,
• the timer should be cleared gracefully in order to avoid setting the setTimeout many times.

AFAIU this is not the case currently