ITrack/Auto updater scripting - Revision history

Dillon Sadofsky: put examples on another line

2010-10-16T03:06:29Z

put examples on another line

← Older revision		Revision as of 22:06, 15 October 2010
Line 13:		Line 13:

	Syntax: run <command>		Syntax: run <command>

	Example: run CD \windows\system		Example: run CD \windows\system

Line 23:		Line 24:

	Syntax: run_delayed <command>		Syntax: run_delayed <command>

	Example: run_delayed CD \windows\system		Example: run_delayed CD \windows\system

Line 31:		Line 33:

	Syntax: runsql <command>		Syntax: runsql <command>

	Example: runsql UPDATE `model` SET `model` = 'Pontiac' WHERE `model` = 'Pontic'		Example: runsql UPDATE `model` SET `model` = 'Pontiac' WHERE `model` = 'Pontic'

Line 39:		Line 42:

	Syntax: addsetting <heading> <keyname> <value>		Syntax: addsetting <heading> <keyname> <value>

	Example: addsetting database logfile C:\Program Files\ISoft Data Systems\mylog.sql		Example: addsetting database logfile C:\Program Files\ISoft Data Systems\mylog.sql

Line 47:		Line 51:

	Syntax: changesetting <heading> <keyname> <value>		Syntax: changesetting <heading> <keyname> <value>

	Example: changesetting database logfile C:\Program Files\ISoft Data Systems\mylog.sql		Example: changesetting database logfile C:\Program Files\ISoft Data Systems\mylog.sql

Line 55:		Line 60:

	Syntax: removesetting <heading> <keyname>		Syntax: removesetting <heading> <keyname>

	Example: removesetting database logfile		Example: removesetting database logfile

	If the setting doesn't exist it is ignored. Also note that the heading and keyname cannot contain whitespace.		If the setting doesn't exist it is ignored. Also note that the heading and keyname cannot contain whitespace.

Dillon Sadofsky: added removesetting and run_delayed

2010-10-16T03:05:45Z

added removesetting and run_delayed

@@ Line 18: / Line 18: @@
 The former is easier to implement and I can't see a disadvantage to it so that's how it will be.  The result of this is that the final thing run in an update script is the batch file.  All other changes are made first.
 == runsql ==
@@ Line 36: / Line 44: @@
 == changesetting ==
-Immediately changes an existing setting in host.ini and also changes the host.ini file lest ITrack shut down improperly.
+Immediately changes an existing setting in memory and also changes the host.ini file lest ITrack shut down improperly.
 Syntax: changesetting <heading> <keyname> <value>
@@ Line 42: / Line 50: @@
 If the setting doesn't exist it is added.  Also note that the heading and keyname cannot contain whitespace.

Duff: /* runsql */ Wrong queries hurt my eyes

2010-05-17T22:01:16Z

runsql: Wrong queries hurt my eyes

← Older revision		Revision as of 17:01, 17 May 2010
Line 23:		Line 23:

	Syntax: runsql <command>		Syntax: runsql <command>
	Example: runsql UPDATE model SET model = 'Pontiac' WHERE model - 'Pontic'		Example: runsql UPDATE `model` SET `model` = 'Pontiac' WHERE `model` = 'Pontic'

	Keep in mind that the sql must occupy exactly one line. Also keep in mind that semi-colons at the end are not necessary and are discouraged.		Keep in mind that the sql must occupy exactly one line. Also keep in mind that semi-colons at the end are not necessary and are discouraged.

Duff: Copied documentation from Charles' text doc

2010-04-01T19:18:21Z

Copied documentation from Charles' text doc

New page

This page contains the syntax for use in the auto-update script files that [[master]] will run on client machines.

These scripts are run as soon as they are downloaded by ITrack, and are not run by the update copier.

Each command must be on a single line. The script parser will strip whitespace from the left side of the line.

If the first non-whitespace character is '#', then the line is considered a comment, and is ignored by the autoupdater.

The first word of the line (which should be the command word) is case-insensitive. If the first word of a line does not match one of these commands or the line is blank (or only whitespace) then the line is ignored.

== run ==
Adds the line to a batch file to run when the script is done being parsed.

Syntax: run <command>
Example: run CD \windows\system

Since often we will have multiple batch statements that rely on previous commands, it is necessary to run these as an entire batch file. The two most reasonable ways to do this are to put ALL run commands from a single update script into a batch file, or to try and group them by their position in the script.

The former is easier to implement and I can't see a disadvantage to it so that's how it will be. The result of this is that the final thing run in an update script is the batch file. All other changes are made first.

== runsql ==
Immediately runs a SQL command against the database.

Syntax: runsql <command>
Example: runsql UPDATE model SET model = 'Pontiac' WHERE model - 'Pontic'

Keep in mind that the sql must occupy exactly one line. Also keep in mind that semi-colons at the end are not necessary and are discouraged.

== addsetting ==
Immediately adds a setting to this computer and also to the host.ini file lest ITrack shut down improperly.

Syntax: addsetting <heading> <keyname> <value>
Example: addsetting database logfile C:\Program Files\ISoft Data Systems\mylog.sql

If the setting already exists, then it is changed. Also note that the heading and keyname cannot contain whitespace.

== changesetting ==
Immediately changes an existing setting in host.ini and also changes the host.ini file lest ITrack shut down improperly.

Syntax: changesetting <heading> <keyname> <value>
Example: changesetting database logfile C:\Program Files\ISoft Data Systems\mylog.sql

If the setting doesn't exist it is added. Also note that the heading and keyname cannot contain whitespace.