Difference between revisions of "Change: Database"
(Created page with "Background:") |
|||
| Line 1: | Line 1: | ||
| − | Background: | + | '''Background:''' |
| + | |||
| + | |||
| + | '''Problems with the current approach:''' | ||
| + | |||
| + | #Redundant weather data. | ||
| + | #Data plan usage can be greatly reduced. | ||
| + | |||
| + | |||
| + | '''Feature Requests:''' | ||
| + | |||
| + | # Be able to rebuild the local database on the hive computer from the public webserver in case of theft or computer failure. | ||
| + | # Be able to send the hive parameters on the local hive to the public database when they are changed locally, and the opposite: | ||
| + | # Be able to send the hive parameters on the public database to the local hive when they are changed in the public database on the public web server. (This allows changing hive parameters and calibration without going in the remote yard or opening a port for access.) | ||
| + | |||
| + | '''Proposed change:''' | ||
Revision as of 08:28, 6 December 2015
Background:
Problems with the current approach:
- Redundant weather data.
- Data plan usage can be greatly reduced.
Feature Requests:
- Be able to rebuild the local database on the hive computer from the public webserver in case of theft or computer failure.
- Be able to send the hive parameters on the local hive to the public database when they are changed locally, and the opposite:
- Be able to send the hive parameters on the public database to the local hive when they are changed in the public database on the public web server. (This allows changing hive parameters and calibration without going in the remote yard or opening a port for access.)
Proposed change:
