oled1 / chia-manager Goto Github PK

Every request should be saved in the subscriptions variable.
The reason is, that it makes no sense, that newly not known connections are terminating in the requests variable.
A newly connected client can't send data to the api without permission anyway.

The GUI should list which plots are reported as damaged or broken on the harvester page.
It should offer the opportunity to detect and delete them.

A user should be able to be deleted and not only be disabled.
A user should be delete-able after previous disabling.

The farmer page should become completely reworked to offer a better overview for all known farmer information.

To make the setup actions as easy as possible for user's an installation bash script should be created which prepares the system for our project with all services which are needed.

When a device will be logged out the line should be removed with DataTables remove function not $(...).remove().
Currently datatable does not recognice it has been deleted.

When the session is not valid anymore the applications stuck at the loading screen when changing page.
The instance should redirect to the login site when changing the page.

Implement a logging subpoint in main menu point system.
On this page the user should be able to see a table about the system log.

If the web-socket server reconnects a standard method called "onWebsocketReconnect" should be implemented on every page which will be called after a reconnect. This function should reload all data on the currently shown page in such case.

Furthermore, the websocket server button on the settings page should be live adapted.

When the sysinfo will be openend, closed and opened again, the charts are not shown.

The json request strings should be changed from:
{'loginStatus': {'status': 0, 'message': 'This node is logged in.', 'data': {'id': '16', 'nodetype': 'Farmer, Harvester, Wallet', 'hostname': 'xch-clien-dev'}}}
To:
{'status': 0, 'method': 'loginStatus', 'message': 'This node is logged in.', 'data': {'id': '16', 'nodetype': 'Farmer, Harvester, Wallet', 'hostname': 'xch-clien-dev'}}

So the clients never have dynamical strings to check. They can always check static json keys.

The project needs to be changed to default npm path to be able to update all modules more easily.

On the following pages the code must be changed twice if the design needs to be changed (PHP on first request and Js on live data change):

• Infra Sysinfo
• Wallet
• Farm
• Harvester

Implement Redis Cache support for caching logs and long term diagram data.
This improves loading times of these.

Chia blockchain software updates should be trigger-able out of the web gui.
Furthermore a setting will be implemented where it is decidable if it should be updated automatically or not.
An additional button for manual upgrading out of the web gui will be implemented on the nodes page in the specific node settings window.

The websocket server seems to be buggy when running in background.
The live data transmission seems to be unfluently.

Implement a markdown language interpreter to show the release notes queried from GitHub correctly.

The wallet page should become completely reworked to offer a better overview for all known wallets.

There should be notifications sent, when:

• a service become critical (e.g. died, not reachable, etc.)
• a service become ok again(e.g. reconnected, etc.)
• the wallet has received some Mojo's or XCH
• ...

A check needs to be implemented which detects if gotify is available on the server.
This notification setting should be able to be enabled in the system settings where default rules (in which case should be alerted or informed) can be applied in the system settings page and be configurable per user base in the Personal Settings.
A user setting needs to be integrated with gotify install and setup instructions (wizard).

The harvester page should become completely reworked to offer a better overview for all known harvester, plots, etc.

Make all API Requests Async including all frontend pages.

There should be notifications sent, when:

• a service become critical (e.g. died, not reachable, etc.)
• a service become ok again(e.g. reconnected, etc.)
• the wallet has received some Mojo's or XCH
• ...

This notification setting should be able to be enabled in the system settings where the API of the third party SMS provider can be stated and default rules (in which case should be alerted or informed) can be applied in the system settings page and be configurable per user base in the Personal Settings.

There should be notifications sent, when:

• a service become critical (e.g. died, not reachable, etc.)
• a service become ok again(e.g. reconnected, etc.)
• the wallet has received some Mojo's or XCH
• ...

This notification setting should be able to be enabled in the system settings where default rules (in which case should be alerted or informed) can be applied in the system settings page and be configurable per user base in the Personal Settings.

Currently on every site where the service status will be checked, it stays Querying Service Status if a node itself is not connected. In such case "Node not connected" should be shown.

Requires Logging fully implemented.

The GUI does not change the colors automatically when changing from/to dark or light GUI mode.

Show all available Pool information in the project which the CHIA RPC Api offers.

Save the following system information to the API and show these values on the Sysinfo page:

• OS type,
• node uptime,
• filesystem type

Show OS icons in the WebGUI

There should be notifications sent, when:

a service become critical (e.g. died, not reachable, etc.)
a service become ok again(e.g. reconnected, etc.)
the wallet has received some Mojo's or XCH
...

This notification setting should be able to be enabled in the system settings where default rules (in which case should be alerted or informed) can be applied in the system settings page and be configurable per user base in the Personal Settings.
A user setting needs to be integrated with gotify install and setup instructions (wizard).

Implement dark mode and Chia specific Colors like green and so on.
The shloud be set to systems default.

The Chia-Manager node client should be fully update able right out of the web GUI.
Furthermore there should be a setting included where you can decide if the node should be automatically updated or not.
The manual update will be trigger-able on the nodes page in the specific Chia-Manager node settings window.

On the system settings page, the email server password can be seen in the element.
This should be removed.

If the user forgot his password he should have the option to reset it.
If a user was newly created, a reset link should be generated and appendend in the invitation mail.