Worker Page Updated #19
Conversation
Added caching for run_often reason for it so you can spam the refresh button (more earlier on resources this way) New Dependencies (psutil, gocept.cache) Changed Readme.md to reflect new dependencies
|
Question: wondering if a worker is offline do we even show a status page the reason i ask this is because let me know what you guys think about this |
|
also to give me suggestions and i will get this fixed |
|
I would keep the page. Later we can show other statistics that do not need
|
Changes: run_info to get_system_load Changes: Added more detailed information in README.md Cleanup: Dashboard code organization Added: Added condition if worker doesn’t exist then show response page instead of error Small Changes: Changes for worker page for refresh button / icon Major Change: Settings page now changes setting and doesn’t error out if you only set one os path Upgrades: upgraded to bootstrap 3.0.2
|
more changes for you guys to look at |
…oved data to worker Changes: removed unneeded comment and corrected print statement Added: Exception for Settings when Setting doesn’t exist in database and corrected debug statements to relate to be more clear
|
more changes / fixes |
Added more worker information like mem usage, cpu usage, load average will tidy up the page within the next couple of days
Added caching for run_often reason for it so you can't spam the refresh button (more earlier on resources this way)
The cache last's for 10 seconds then you can refresh again
New Dependencies (psutil, gocept.cache)
Changed Readme.md to reflect new dependencies