Scripts usage - Revision history

KKoPV: /* Scripts for data saving */

2016-08-05T12:44:31Z

‎Scripts for data saving

KKoPV: /* Configuration Template */

2016-08-05T12:44:01Z

‎Configuration Template

KKoPV at 12:43, 5 August 2016

2016-08-05T12:43:33Z

KKoPV: /* Initial test */

2016-08-05T12:39:11Z

‎Initial test

KKoPV: KKoPV moved page Testing scripts to Scripts usage without leaving a redirect

2016-08-05T12:37:18Z

KKoPV moved page Testing scripts to Scripts usage without leaving a redirect

KKoPV: /* Scripts for data saving */

2016-08-05T12:35:17Z

‎Scripts for data saving

KKoPV: /* Scripts for data saving */

2016-08-05T12:34:44Z

‎Scripts for data saving

KKoPV: /* Scripts for data saving */

2016-08-05T12:34:03Z

‎Scripts for data saving

KKoPV: /* Common parameters */

2016-08-05T12:33:09Z

‎Common parameters

KKoPV at 12:32, 5 August 2016

2016-08-05T12:32:23Z

@@ Line 23: / Line 23: @@
 More information, multiple <code>-v</code> increase up to level 3, which then also makes cUrl calls verbose.
-=== Scripts for data saving ===
+=== Data saving scripts ===
 Data gathering scripts can run on different equipments than the API, e.g. on a Raspberry or so.

@@ Line 1: / Line 1: @@
 {{TOCright}}[[Category:Scripts]]
-== Configuration Template ==
+== Configuration ==
 A configuration template for each script is available in the corresponding <code>dist/</code> directory.

← Older revision		Revision as of 12:43, 5 August 2016
Line 40:		Line 40:
	$ ./script.sh -tvc config.conf # Test with defined configuration, verbose level 2		$ ./script.sh -tvc config.conf # Test with defined configuration, verbose level 2
	$ ./script.sh -tvv # Test with verbose level 3 also shows cUrl details		$ ./script.sh -tvv # Test with verbose level 3 also shows cUrl details
		+
		+	== Productive use ==
		+
		+	By default (without <code>-v</code> flag) no output is produced at all.
		+
		+	So you can run any script in crontab without redirecting the output. '''But if''' there is any output, then an error occurred...

@@ Line 35: / Line 35: @@
 Save the data also locally, this is helpful if the connection to the API server is not stable. Missing data can loaded later manually.
-== Initial test ==
+== Test ==
   $ ./script.sh -t                # Simple test with default configuration, verbose level 1
   $ ./script.sh -tvc config.conf  # Test with defined configuration, verbose level 2
   $ ./script.sh -tvv              # Test with verbose level 3 also shows cUrl details

@@ Line 29: / Line 29: @@
   -l, --localtime          Use local time, rounded to ? seconds [default:0]
-You can define that the "local" time will be used.<br />You can for example also define, that the local timestamp always is rounded to full minute with <code>--localtime 60</code>
+You can define that the "local" time will be used.<br />You can for example also define, that the local timestamp always is rounded to full minute with <code> --localtime 60</code>
   -s, --save               Save data also into log file [flag]

← Older revision	Revision as of 12:37, 5 August 2016
(No difference)

@@ Line 4: / Line 4: @@
 A configuration template for each script is available in the corresponding <code>dist/</code> directory.
-== Common parameters ==
+== Parameters ==
 These parameters work with all scripts, for writing data to and reading from PVLng API.

@@ Line 1: / Line 1: @@
-[[Category:Scripts]]
+{{TOCright}}[[Category:Scripts]]
 == Configuration Template ==
 A configuration template for each script is available in the corresponding <code>dist/</code> directory.
-== Data gathering scripts ==
+== Common parameters ==
-Mostly all scripts that gather data from equipments to store into PVLng support the following parameters.
+These parameters work with all scripts, for writing data to and reading from PVLng API.
   -c, --config             Config file [default:script.conf]
-The default configuration file file depends on the concrete script file name, so for an <code>update.sh</code> the default configuration file is <code>update.conf</code>
+The default configuration file name depends on the concrete script file name, so for an <code>update.sh</code> the default configuration file will be <code>update.conf</code>
-  -l, --localtime          Use local time, rounded to ? seconds [default:0]
+  -t, --test               Test mode, set verbosity to info level [flag]
-If you gather the data with external hardware (e.g. a Raspberry), you can define that the "lokal" time will be used.
+Gather only the data, make required transformations and display what would be send to the API server.
-You can for example also define, that the timestamp always is rounded to full minute with <code>-l 60</code>.
+Set also verbosity to level 1.
-  -s, --save               Save data also into log file [flag]
+  -v, --verbose            Verbosity, use multiple times for higher level [flag]
-This is helpful, if the connection to the API server is not stable. This help to load missing data later.
+More information, multiple <code>-v</code> increase up to level 3, which then also makes cUrl calls verbose.
- -t, --test               Test mode, set verbosity to info level [flag]
+=== Scripts for data saving ===
-Gather only the data, make required transformations and display what would be send to the API server.
+Data gathering scripts can run on different equipments than the API, e.g. on a Raspberry or so.
-  -v, --verbose            Verbosity, use multiple times for higher level [flag]
+  -l, --localtime          Use local time, rounded to ? seconds [default:0]
-More information, multiple <code>-v</code> increase up to level 3
+If you gather the data with external hardware (e.g. a Raspberry), you can define that the "lokal" time will be used.
-== Data readout scripts ==
+ -s, --save               Save data also into log file [flag]
 == Initial test ==