Unimore PLE/Docs/Tools/CoDeploy - Revision history

44736 at 13:28, 2 November 2009

2009-11-02T13:28:20Z

← Older revision		Revision as of 13:28, 2 November 2009
Line 6:		Line 6:
	<br>So, if you have: <b>DocumentRoot /var/www/</b>		<br>So, if you have: <b>DocumentRoot /var/www/</b>
	<br>then replace with <b>DocumentRoot /home/yourUserName/choosenFolder/</b>		<br>then replace with <b>DocumentRoot /home/yourUserName/choosenFolder/</b>
	<br>This should work just fine if your Linux box is being used by a single user.		<br>This should work just fine if your Linux box is being used by a single user. After that, you should be able to view a sample index.html file, that you save into "choosenFolder", with a Web browser by connecting to the IP of your local host. Be sure that you can view it when connecting from outside your LAN: if you can't, then the firewall is blocking your port 80.

	The syntax of the CoDeploy command is something like this: <i>codeploy -a localDirectory http://localHostIP_orName/localDirectory/ remoteDirectory</i>.		The syntax of the CoDeploy command is something like this: <i>codeploy -a localDirectory http://localHostIP_orName/localDirectory/ remoteDirectory</i>.
	<br>With -a you specify you want to send compressed data, useful if deploying large files for the first time. <i>localDirectory</i> is the directory containing the files you want to be deployed and MUST be inside the "choosenFolder" with which you configured DocumentRoot, the URL is where remote nodes will find the files and <i>remoteDirectory</i> is the remote directory where the files will be copied.		<br>With -a you specify you want to send compressed data, useful if deploying large files for the first time; <i>localDirectory</i> is the directory containing the files you want to be deployed and MUST be inside the "choosenFolder" with which you configured the DocumentRoot; the URL is where remote nodes will find the files and <i>remoteDirectory</i> is the remote directory where the files will be copied. Before issuing the command, you can check if the files are in the correct folder by opening with a Web browser the page <b>http://localHostIP_orName/localDirectory/</b>, it should display the list of files that you want to transfer.

			CoDeploy then generates a script that is copied to the remote nodes and then executed, for downloading the files from hosts of a CDN ([http://codeen.cs.princeton.edu/ CoDeen]) or from the local host. It seems to be a quite slow method compared to MultiCopy, but maybe it depends on the volume of data to be transferred.

	work in progress		work in progress

44736 at 11:29, 2 November 2009

2009-11-02T11:29:34Z

← Older revision		Revision as of 11:29, 2 November 2009
Line 4:		Line 4:

	You have to setup the HTTP server so that, when you give an URL pointing to a directory on your local host, then this can be find by remote nodes. On Ubuntu, you have to modify the file <i>/etc/apache2/sites-available/default</i> so that the "DocumentRoot" parameter, which by default is /var/www/, points e.g. to your PlanetLab directory.		You have to setup the HTTP server so that, when you give an URL pointing to a directory on your local host, then this can be find by remote nodes. On Ubuntu, you have to modify the file <i>/etc/apache2/sites-available/default</i> so that the "DocumentRoot" parameter, which by default is /var/www/, points e.g. to your PlanetLab directory.
	<br>If you have: <i>DocumentRoot /var/www/</i>		<br>So, if you have: <b>DocumentRoot /var/www/</b>
	<br>replace with <i>DocumentRoot /home/yourUserName/choosenFolder/</i>		<br>then replace with <b>DocumentRoot /home/yourUserName/choosenFolder/</b>
	<br>This should work fine if your Linux box is being used by a single user.		<br>This should work just fine if your Linux box is being used by a single user.

	The syntax of the CoDeploy command is something like this: <i>codeploy -a localDirectory http://localHostIP_orName/localDirectory/ remoteDirectory</i>.		The syntax of the CoDeploy command is something like this: <i>codeploy -a localDirectory http://localHostIP_orName/localDirectory/ remoteDirectory</i>.

44736 at 11:28, 2 November 2009

2009-11-02T11:28:42Z

← Older revision		Revision as of 11:28, 2 November 2009
Line 2:		Line 2:

	CoDeploy needs an HTTP server, such as Apache2, running on the local host containing the software to be deployed. So, if you are behind a firewall, you need to have the port 80 of the local host "open" so that remote machines can access contents by mean of an HTTP connection, as if they are downloading a file from a Web site.		CoDeploy needs an HTTP server, such as Apache2, running on the local host containing the software to be deployed. So, if you are behind a firewall, you need to have the port 80 of the local host "open" so that remote machines can access contents by mean of an HTTP connection, as if they are downloading a file from a Web site.

			You have to setup the HTTP server so that, when you give an URL pointing to a directory on your local host, then this can be find by remote nodes. On Ubuntu, you have to modify the file <i>/etc/apache2/sites-available/default</i> so that the "DocumentRoot" parameter, which by default is /var/www/, points e.g. to your PlanetLab directory.
			<br>If you have: <i>DocumentRoot /var/www/</i>
			<br>replace with <i>DocumentRoot /home/yourUserName/choosenFolder/</i>
			<br>This should work fine if your Linux box is being used by a single user.

			The syntax of the CoDeploy command is something like this: <i>codeploy -a localDirectory http://localHostIP_orName/localDirectory/ remoteDirectory</i>.
			<br>With -a you specify you want to send compressed data, useful if deploying large files for the first time. <i>localDirectory</i> is the directory containing the files you want to be deployed and MUST be inside the "choosenFolder" with which you configured DocumentRoot, the URL is where remote nodes will find the files and <i>remoteDirectory</i> is the remote directory where the files will be copied.

	work in progress		work in progress

44736 at 10:08, 2 November 2009

2009-11-02T10:08:10Z

← Older revision		Revision as of 10:08, 2 November 2009
Line 1:		Line 1:
	<accesscontrol>luser</accesscontrol>		<accesscontrol>luser</accesscontrol>

			CoDeploy needs an HTTP server, such as Apache2, running on the local host containing the software to be deployed. So, if you are behind a firewall, you need to have the port 80 of the local host "open" so that remote machines can access contents by mean of an HTTP connection, as if they are downloading a file from a Web site.

			work in progress

44736 at 09:51, 2 November 2009

2009-11-02T09:51:18Z

← Older revision	Revision as of 09:51, 2 November 2009
Line 1:	Line 1:
		<accesscontrol>luser</accesscontrol>

44736: Blanked the page

2009-11-02T09:48:32Z

Blanked the page

← Older revision		Revision as of 09:48, 2 November 2009
Line 1:		Line 1:
	~~<accesscontrol>luser</accesscontrol>~~

44736: Created page with 'luser'

2009-11-02T09:37:46Z

Created page with '<accesscontrol>luser</accesscontrol>'

New page

<accesscontrol>luser</accesscontrol>