Personal tools

Difference between revisions of "Installation"

From PhotoVoltaic Logger new generation

Jump to: navigation, search
m (Software requirements)
m (Core repository)
 
(13 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
* MySQL ≥ 5.1 (supports table partitions, views, trigger, functions, procedures and events)
 
* MySQL ≥ 5.1 (supports table partitions, views, trigger, functions, procedures and events)
 
* PHP ≥ 5.3
 
* PHP ≥ 5.3
* Web server with PHP support, tested with Apache, Litespeed and Nginx (recommended)
+
* Web server with PHP support, tested with Nginx (recommended), Apache and Litespeed
  
''See also these [[Software hints|hints]] for details!''
+
'''See also these [[Software hints|hints]] for details!'''
  
 
== Hardware requirements ==
 
== Hardware requirements ==
* A server, which fits the software requirements :-)
+
* A server, which fits the software requirements :-)<br />A Raspberry B with a 4 GB SD card works fine for me as scripts server connected to a central frontend/API sever.
 
* Some sensors, like [[1-Wire sensor]]s, watt meters with [[S0 reader|S0]] or [[D0 reader|D0]] outputs
 
* Some sensors, like [[1-Wire sensor]]s, watt meters with [[S0 reader|S0]] or [[D0 reader|D0]] outputs
 
* Solar inverter which supports either
 
* Solar inverter which supports either
** live query of data ([[SMA Webbox]], [[Grouping models#Fronius\SolarNet|Fronius]], [[Grouping models#Kaco|Kaco]])
+
** live query of data ([[SMA Webbox]], [[Grouping models#Fronius\SolarNet|Fronius]], [[Grouping models#Kaco|Kaco]], [[Grouping models#Kostal|Kostal]])
 
** write data in short intervals (quasi-live) somewhere
 
** write data in short intervals (quasi-live) somewhere
  
 
== Installation ==
 
== Installation ==
  
The system is devided into 2 repositories, the PVLng core repo with [[:Category:Web_frontend|web frontend]] and [[API]] and the [[:Category:Scripts|PVLng-Scripts]] repo with the data aquisition scripts.
+
The system is devided into 2 repositories, the PVLng core repo with [[:Category:Web_frontend|web frontend]] and [[API]] and the [[:Category:Scripts|PVLng-Scripts]] repo with the data aquisition and extraction scripts.
  
 
* [[Core repository installation instructions|Installation instructions]] for {{PVLngRepo}}
 
* [[Core repository installation instructions|Installation instructions]] for {{PVLngRepo}}
Line 24: Line 24:
 
[[Category:Hardware]]
 
[[Category:Hardware]]
 
[[Category:Software]]
 
[[Category:Software]]
 +
 +
== Upgrade ==
 +
=== Core repository ===
 +
Your can upgrade your installation at any time with
 +
 +
$ tools/upgrade.git
 +
 +
Upgrade your installation to lastest state from Github.
 +
 +
Usage: tools/upgrade.git <branch>
 +
 +
This works with <tt>master</tt> and <tt>develop</tt>
 +
* Checkout the lastest changes from GitHub
 +
* Apply outstanding database patches if any
 +
 +
=== Scripts repository ===
 +
 +
Just pull the latest changes from GitHub
 +
git checkout master
 +
or
 +
git checkout develop
 +
and
 +
git pull

Latest revision as of 20:23, 6 August 2016

Software requirements

  • Operating system with support of periodic job scheduling (for example *nix with cron)
  • MySQL ≥ 5.1 (supports table partitions, views, trigger, functions, procedures and events)
  • PHP ≥ 5.3
  • Web server with PHP support, tested with Nginx (recommended), Apache and Litespeed

See also these hints for details!

Hardware requirements

  • A server, which fits the software requirements :-)
    A Raspberry B with a 4 GB SD card works fine for me as scripts server connected to a central frontend/API sever.
  • Some sensors, like 1-Wire sensors, watt meters with S0 or D0 outputs
  • Solar inverter which supports either

Installation

The system is devided into 2 repositories, the PVLng core repo with web frontend and API and the PVLng-Scripts repo with the data aquisition and extraction scripts.

Upgrade

Core repository

Your can upgrade your installation at any time with

$ tools/upgrade.git

Upgrade your installation to lastest state from Github.

Usage: tools/upgrade.git <branch>

This works with master and develop

  • Checkout the lastest changes from GitHub
  • Apply outstanding database patches if any

Scripts repository

Just pull the latest changes from GitHub

git checkout master

or

git checkout develop

and

git pull