WordPress site on Google Cloud - setup Node JS and correct console errors
Budget: $74 – $75 AUD
On my site I have a chat feature that requires Node to be running so that messages and attachments are delivered live, instantly without page refresh. However, when server is disconnected for some reason node stops, even after server is restarted. Node does not start automatically, it has to be restarted according to the instructions attached whenever server is restarted.
In this task you will do the following.
First, you need to activate Node JS and restart it manually as per instructions. You only have to focus on setting up Node and restarting it according to provided instructions ("NODE JS setup instructions.docx"). Those instructions were created when site was on shared host server but they worked for that server as well as when the site was transferred to Amazon AWS server. When Node is running, messages and attachments will be arriving instantly without page refresh. Once running, you need to create CRON job or similar in order to restart Node automatically when server restarts next time so that we don’t have to manually restart Node whenever server restarts.
Second, you need to fix some errors on the console. Some of these errors may be fixed once Node is activated BUT you have to fix ALL of them. These errors may be causing page freezing issues. We will know this task is done when console errors are removed and page elements no longer freeze (images starting with “2.”). Many of the errors point to “3000 socket IO”. Maybe this has to do with opening the socket or something like that. You figure out.
In this task you will do the following.
First, you need to activate Node JS and restart it manually as per instructions. You only have to focus on setting up Node and restarting it according to provided instructions ("NODE JS setup instructions.docx"). Those instructions were created when site was on shared host server but they worked for that server as well as when the site was transferred to Amazon AWS server. When Node is running, messages and attachments will be arriving instantly without page refresh. Once running, you need to create CRON job or similar in order to restart Node automatically when server restarts next time so that we don’t have to manually restart Node whenever server restarts.
Second, you need to fix some errors on the console. Some of these errors may be fixed once Node is activated BUT you have to fix ALL of them. These errors may be causing page freezing issues. We will know this task is done when console errors are removed and page elements no longer freeze (images starting with “2.”). Many of the errors point to “3000 socket IO”. Maybe this has to do with opening the socket or something like that. You figure out.