There are many messages in web browser console.
It would be great to hide them in the deployed instance.
After finishing the tests, we could simply comment them out.
Edited
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
Please implement a logger module if there isn't one. Since our project is now live and public, we should log errors/warnings in standard rotating log files, so we can trace back and find the root causes of the issues reported by users.
Also, definitely no console-logs on productions (urgently remove) !!!
Yes for the part of code running on the browser, we avoid console.log
But for those running on the server, we should have a logger (for eg, strapi part)
Regarding strapi, now we collect the logs and logrotate runs 'Log rotation'.
Dev CMS : /home/ddcode-dev/dd-code/cms-logs/cms-dev.log
Prod CMS : /home/local/dd-code/cms-logs/cms.log
The reason to use the parent folder of cms is that STRAPI checks the file changes and tries to restart the server process whenever the log file is changed.