Installing LXW - Revision history

Codeman: Redirecting the LXW install page

2015-04-09T22:23:06Z

Redirecting the LXW install page

← Older revision		Revision as of 17:23, 9 April 2015
Line 1:		Line 1:
	~~The new version of ITrack LX, colloquially known as LXW, is the faster and sexier version of ITrack designed to run in the browser, primarily on handheld scanner devices.~~		#REDIRECT [[Internal:Installing LXW]]

	~~== Dependencies ==~~
	~~Besides the regular version of~~ [[~~MySQL]] used by ITrack Enterprise, LXW requires~~:
	* [http://httpd.apache.org/download.cgi Apache] 2.2 or higher
	* [http://php.net/downloads.php PHP] 5.3 or higher
	* [http://subversion.apache.org/ SVN] 1.6 or higher

	== Installing ~~the client-side code ==~~
	~~This is the code that is accessible via HTTP! Check it out to your Apache htdocs folder, or whatever other folder will get it served up to the tubes.~~

	~~The directory to check out is [https://svn.isoftdata.com/Web/javascript-trunk/lxw https://svn.isoftdata.com/Web/javascript-trunk/lxw].~~

	~~To configure the connection to the server-side code: edit line 15 of server/index.php to point it at the path where you checked out the server-side code.~~

	~~To configure client application settings (which should all have reasonable defaults), you can edit the config.js file in the client path.~~

	~~== Installing the server-side code ==~~
	~~This is the PHP code that talks to the database! It should be checked out somewhere that is ''not'' accessible via HTTP.~~

	~~Put all three directories in a single directory "lxwserver" for example somewhere that is ''not'' accessible via HTTP.~~

	~~The directory to check out is [https://svn.isoftdata.com/Web/tinymvc-trunk/lxw https://svn.isoftdata.com/Web/tinymvc-trunk/lxw].~~

	~~I believe you need more than just the lxw directory listed above.~~
	~~you also need the https://svn.isoftdata.com/Web/tinymvc-trunk/sysfiles directory.~~

	~~And possibly https://svn.isoftdata.com/Web/tinymvc-trunk/myfiles/ as well.~~

	~~To configure the database connection, edit /lxw/configs/database.php.~~

	~~== Setting Up the Auto-Updater ==~~
	~~'''Use with care: The AU process for LXW is not well-explored!'''~~

	~~This is the process that will download updates for~~ LXW ~~and then install them.~~

	~~[https://svn.isoftdata.com/Web/javascript-trunk/isoft-updater-example/ https://svn.isoftdata.com/Web/javascript-trunk/isoft-updater-example/~~]

	~~#Transfer contents of this directory to the server hosting LXW. The standard directory for Linux based servers is /var/www/lxw/updater (This directory will not exist yet.)~~
	~~#Configure config.json~~
	~~#Run the .sh files~~
	~~##install.sh~~
	~~##run.sh~~
	~~#Add updater to crontab~~

	~~===Configure config.json ===~~
	~~An example of a config.json~~

	~~<code lang="json">~~

	{
	~~"update_url": "autoupdate URL here",~~
	~~"product_code": "valid product code here",~~
	~~"download_directory": "/var/www/lxw-release/updater/downloaded-all",~~
	~~"destination_directories": {~~
	~~"default": "/var/www/lxw-release/updater/downloaded-latest",~~
	},
	~~"extraction_directories": {~~
	~~"LXW-client.zip": "/var/www/html/lxw",~~
	~~"LXW-server.zip": "/var/www/lxw-release"~~
	}
	}
	~~</code>~~

	~~After the updater is run properly then a new section will appear below this section and it will look like this.~~

	~~<code>~~

	~~"versions": {~~
	~~"LXW-client.zip": "#####",~~
	~~"LXW-server.zip": "#####"~~
	}

	~~</code>~~

	~~===Run .sh Files===~~
	Unfortunately as of February 25th 2013 you are unable to run the .sh files as they will be unable to find the config file. Instead you can run the contents of the files without any problem. Here is an example of each file as you would use it for LKQ.

	~~'''install.sh'''~~
	~~<code>~~
	~~sudo npm install isoft-updater -g~~
	~~</code>~~

	~~'''run.sh'''~~
	~~<code>~~
	~~node /lib/node_modules/isoft-updater /var/www/lxw-release/updater/config.json~~
	~~</code>~~

	~~===Add Updater to Crontab===~~
	~~The last bit to setting up the auto updater is the "auto" part. Here is how to access and edit the crontab.~~

	~~<code>~~
	~~crontab -e~~
	~~</code>~~

	~~This is what LKQ's crontab looks like for the autoupdater.~~
	~~<code>~~
	~~12 21 * * * node /lib/node_modules/isoft-updater /var/www/lxw-release/updater/config.json~~
	~~</code>~~

	~~This is the format that crontab uses.~~

	~~<code>~~
	* * * * * command to be executed
	~~- - - - -~~
	~~\| \| \| \| \|~~
	~~\| \| \| \| +----- day of week (0 - 6) (Sunday=0)~~
	~~\| \| \| +------- month (1 - 12)~~
	~~\| \| +--------- day of month (1 - 31)~~
	~~\| +----------- hour (0 - 23)~~
	~~+------------- min (0 - 59)~~
	~~</code>~~

	~~====Note====~~
	~~Removing the version section in config.json will cause it to redownload the latest update during the next scheduled update cycle or forced update. Can be used to test the process.~~

	~~== Testing ==~~
	~~Browsing to the [the URL you would expect to correspond to the client-side files you installed~~]~~/server/index.php should show you a snide remark embedded in JSON.~~

	~~Browsing to the regular URL should show you a screen asking you to identify your store number (assuming that your web server is configured to serve up index.html files when you browse to a directory).~~

Jwise: /* Installing the server-side code */

2014-08-21T16:31:34Z

Installing the server-side code

← Older revision		Revision as of 11:31, 21 August 2014
Line 18:		Line 18:
	== Installing the server-side code ==		== Installing the server-side code ==
	This is the PHP code that talks to the database! It should be checked out somewhere that is ''not'' accessible via HTTP.		This is the PHP code that talks to the database! It should be checked out somewhere that is ''not'' accessible via HTTP.

			Put all three directories in a single directory "lxwserver" for example somewhere that is ''not'' accessible via HTTP.

	The directory to check out is [https://svn.isoftdata.com/Web/tinymvc-trunk/lxw https://svn.isoftdata.com/Web/tinymvc-trunk/lxw].		The directory to check out is [https://svn.isoftdata.com/Web/tinymvc-trunk/lxw https://svn.isoftdata.com/Web/tinymvc-trunk/lxw].

			I believe you need more than just the lxw directory listed above.
			you also need the https://svn.isoftdata.com/Web/tinymvc-trunk/sysfiles directory.

			And possibly https://svn.isoftdata.com/Web/tinymvc-trunk/myfiles/ as well.

	To configure the database connection, edit /lxw/configs/database.php.		To configure the database connection, edit /lxw/configs/database.php.

Jmckinstry: Updating to reflect the current state of affairs of LXW

2014-06-24T18:56:32Z

Updating to reflect the current state of affairs of LXW

← Older revision		Revision as of 13:56, 24 June 2014
Line 5:		Line 5:
	* [http://httpd.apache.org/download.cgi Apache] 2.2 or higher		* [http://httpd.apache.org/download.cgi Apache] 2.2 or higher
	* [http://php.net/downloads.php PHP] 5.3 or higher		* [http://php.net/downloads.php PHP] 5.3 or higher
	* [http://nodejs.org/download/ Node.js] 0.8 or higher
	* [http://subversion.apache.org/ SVN] 1.6 or higher		* [http://subversion.apache.org/ SVN] 1.6 or higher

	~~== Installing the server-side code ==~~
	~~This is the PHP code that talks to the database! It should be checked out somewhere that is ''not'' accessible via HTTP.~~

	~~The directory to check out is [https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release].~~

	~~To configure the database connection, edit /lxw/configs/database.php.~~

	== Installing the client-side code ==		== Installing the client-side code ==
	This is the code that is accessible via HTTP! Check it out to your Apache htdocs folder, or whatever other folder will get it served up to the tubes.		This is the code that is accessible via HTTP! Check it out to your Apache htdocs folder, or whatever other folder will get it served up to the tubes.

	The directory to check out is [https://svn.isoftdata.com~~/svn~~/Web/~~tinymvc-branches/lxw~~-~~release~~/lxw~~/client~~ https://svn.isoftdata.com~~/svn~~/Web/~~tinymvc-branches/lxw~~-~~release~~/lxw~~/client~~].		The directory to check out is [https://svn.isoftdata.com/Web/javascript-trunk/lxw https://svn.isoftdata.com/Web/javascript-trunk/lxw].

	To configure the connection to the server-side code: edit line 15 of server/index.php to point it at the path where you checked out the server-side code.		To configure the connection to the server-side code: edit line 15 of server/index.php to point it at the path where you checked out the server-side code.

	To configure client application settings (which should all have reasonable defaults), you can edit the config.js file in the client path.		To configure client application settings (which should all have reasonable defaults), you can edit the config.js file in the client path.

			== Installing the server-side code ==
			This is the PHP code that talks to the database! It should be checked out somewhere that is ''not'' accessible via HTTP.

			The directory to check out is [https://svn.isoftdata.com/Web/tinymvc-trunk/lxw https://svn.isoftdata.com/Web/tinymvc-trunk/lxw].

			To configure the database connection, edit /lxw/configs/database.php.

	== Setting Up the Auto-Updater ==		== Setting Up the Auto-Updater ==
			'''Use with care: The AU process for LXW is not well-explored!'''

	This is the process that will download updates for LXW and then install them.		This is the process that will download updates for LXW and then install them.

Duff: /* Configure config.json */ Removing unnecessary data

2013-03-01T17:09:43Z

Configure config.json: Removing unnecessary data

← Older revision		Revision as of 12:09, 1 March 2013
Line 37:		Line 37:

	===Configure config.json ===		===Configure config.json ===
	An example of ~~LKQ's~~ config.json		An example of a config.json

	<code>		<code lang="json">

	{		{
	"update_url": "~~https://isupdate:UpD8Me@www.isoftdata.com:443/~~autoupdate~~/update.php~~",		"update_url": "autoupdate URL here",
	"product_code": "~~8298525~~",		"product_code": "valid product code here",
	"download_directory": "/var/www/lxw-release/updater/downloaded-all",		"download_directory": "/var/www/lxw-release/updater/downloaded-all",
	"destination_directories": {		"destination_directories": {
	"default": "/var/www/lxw-release/updater/downloaded-latest"/*,		"default": "/var/www/lxw-release/updater/downloaded-latest",
	},		},
	"extraction_directories": {		"extraction_directories": {

Dfleischman: Added the Note section

2013-02-26T22:50:52Z

Added the Note section

← Older revision		Revision as of 17:50, 26 February 2013
Line 103:		Line 103:
	+------------- min (0 - 59)		+------------- min (0 - 59)
	</code>		</code>

			====Note====
			Removing the version section in config.json will cause it to redownload the latest update during the next scheduled update cycle or forced update. Can be used to test the process.

	== Testing ==		== Testing ==

Dfleischman: Substituted all sample version numbers with #'s

2013-02-26T20:34:01Z

Substituted all sample version numbers with #'s

← Older revision		Revision as of 15:34, 26 February 2013
Line 60:		Line 60:

	"versions": {		"versions": {
	"LXW-client.zip": "27###",		"LXW-client.zip": "#####",
	"LXW-server.zip": "27###"		"LXW-server.zip": "#####"
	}		}

Dfleischman: Formatting fixes and added crontab format

2013-02-26T20:04:57Z

Formatting fixes and added crontab format

← Older revision		Revision as of 15:04, 26 February 2013
Line 86:		Line 86:
	</code>		</code>

	This is what LKQ's crontab looks like for the autoupdater		This is what LKQ's crontab looks like for the autoupdater.
	<code>		<code>
	12 21 * * * node /lib/node_modules/isoft-updater /var/www/lxw-release/updater/config.json		12 21 * * * node /lib/node_modules/isoft-updater /var/www/lxw-release/updater/config.json
			</code>

			This is the format that crontab uses.

			<code>
			* * * * * command to be executed
			- - - - -
			\| \| \| \| \|
			\| \| \| \| +----- day of week (0 - 6) (Sunday=0)
			\| \| \| +------- month (1 - 12)
			\| \| +--------- day of month (1 - 31)
			\| +----------- hour (0 - 23)
			+------------- min (0 - 59)
	</code>		</code>

Dfleischman: Added how to setup the autoupdater

2013-02-26T02:19:10Z

Added how to setup the autoupdater

← Older revision		Revision as of 21:19, 25 February 2013
Line 23:		Line 23:

	To configure client application settings (which should all have reasonable defaults), you can edit the config.js file in the client path.		To configure client application settings (which should all have reasonable defaults), you can edit the config.js file in the client path.

			== Setting Up the Auto-Updater ==
			This is the process that will download updates for LXW and then install them.

			[https://svn.isoftdata.com/Web/javascript-trunk/isoft-updater-example/ https://svn.isoftdata.com/Web/javascript-trunk/isoft-updater-example/]

			#Transfer contents of this directory to the server hosting LXW. The standard directory for Linux based servers is /var/www/lxw/updater (This directory will not exist yet.)
			#Configure config.json
			#Run the .sh files
			##install.sh
			##run.sh
			#Add updater to crontab

			===Configure config.json ===
			An example of LKQ's config.json

			<code>

			{
			"update_url": "https://isupdate:UpD8Me@www.isoftdata.com:443/autoupdate/update.php",
			"product_code": "8298525",
			"download_directory": "/var/www/lxw-release/updater/downloaded-all",
			"destination_directories": {
			"default": "/var/www/lxw-release/updater/downloaded-latest"/*,
			},
			"extraction_directories": {
			"LXW-client.zip": "/var/www/html/lxw",
			"LXW-server.zip": "/var/www/lxw-release"
			}
			}
			</code>

			After the updater is run properly then a new section will appear below this section and it will look like this.

			<code>

			"versions": {
			"LXW-client.zip": "27###",
			"LXW-server.zip": "27###"
			}

			</code>

			===Run .sh Files===
			Unfortunately as of February 25th 2013 you are unable to run the .sh files as they will be unable to find the config file. Instead you can run the contents of the files without any problem. Here is an example of each file as you would use it for LKQ.

			'''install.sh'''
			<code>
			sudo npm install isoft-updater -g
			</code>

			'''run.sh'''
			<code>
			node /lib/node_modules/isoft-updater /var/www/lxw-release/updater/config.json
			</code>

			===Add Updater to Crontab===
			The last bit to setting up the auto updater is the "auto" part. Here is how to access and edit the crontab.

			<code>
			crontab -e
			</code>

			This is what LKQ's crontab looks like for the autoupdater
			<code>
			12 21 * * * node /lib/node_modules/isoft-updater /var/www/lxw-release/updater/config.json
			</code>

	== Testing ==		== Testing ==

Broy: SVN should be accessed in a secure manner, ideally.

2012-09-26T17:58:19Z

SVN should be accessed in a secure manner, ideally.

← Older revision		Revision as of 12:58, 26 September 2012
Line 11:		Line 11:
	This is the PHP code that talks to the database! It should be checked out somewhere that is ''not'' accessible via HTTP.		This is the PHP code that talks to the database! It should be checked out somewhere that is ''not'' accessible via HTTP.

	The directory to check out is [~~http~~://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release ~~http~~://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release].		The directory to check out is [https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release].

	To configure the database connection, edit /lxw/configs/database.php.		To configure the database connection, edit /lxw/configs/database.php.
Line 18:		Line 18:
	This is the code that is accessible via HTTP! Check it out to your Apache htdocs folder, or whatever other folder will get it served up to the tubes.		This is the code that is accessible via HTTP! Check it out to your Apache htdocs folder, or whatever other folder will get it served up to the tubes.

	The directory to check out is [~~http~~://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release/lxw/client ~~http~~://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release/lxw/client].		The directory to check out is [https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release/lxw/client https://svn.isoftdata.com/svn/Web/tinymvc-branches/lxw-release/lxw/client].

	To configure the connection to the server-side code: edit line 15 of server/index.php to point it at the path where you checked out the server-side code.		To configure the connection to the server-side code: edit line 15 of server/index.php to point it at the path where you checked out the server-side code.

Duff: /* Dependencies */ We actually can work with SVN 1.6 or better

2012-09-25T16:26:56Z

Dependencies: We actually can work with SVN 1.6 or better

← Older revision		Revision as of 11:26, 25 September 2012
Line 6:		Line 6:
	* [http://php.net/downloads.php PHP] 5.3 or higher		* [http://php.net/downloads.php PHP] 5.3 or higher
	* [http://nodejs.org/download/ Node.js] 0.8 or higher		* [http://nodejs.org/download/ Node.js] 0.8 or higher
	* [http://subversion.apache.org/ SVN] 1.7 or higher		* [http://subversion.apache.org/ SVN] 1.6 or higher

	== Installing the server-side code ==		== Installing the server-side code ==