Migration to Web Farm 2 - Revision history

Cheeks: /* =Perl Notes */

2009-06-03T17:48:13Z

=Perl Notes

← Older revision		Revision as of 11:48, 3 June 2009
Line 81:		Line 81:
	** Older versions of the '''phpWebSite''' CMS have a bug in the calendar module (completely different from the PHP-Nuke problem). Causes infinite loop when you access the calendar. Current version of phpWebSite is believed to be OK.		** Older versions of the '''phpWebSite''' CMS have a bug in the calendar module (completely different from the PHP-Nuke problem). Causes infinite loop when you access the calendar. Current version of phpWebSite is believed to be OK.

	====Perl Notes===		====Perl Notes====
	If you are using the CGI::Session library, and you are using a MySQL table to store session data, the table needs to be on a MySQL 5 server. If your database is currently on mysql.swcp.com, let us know and we can move your database to mysql5.swcp.com which is our MySQL 5 server. there might be other ramifications to this if you have other code which uses MySQL. There are a few compatibility between MySQL 4 and 5, but most of them are easily overcome.		If you are using the CGI::Session library, and you are using a MySQL table to store session data, the table needs to be on a MySQL 5 server. If your database is currently on mysql.swcp.com, let us know and we can move your database to mysql5.swcp.com which is our MySQL 5 server. there might be other ramifications to this if you have other code which uses MySQL. There are a few compatibility between MySQL 4 and 5, but most of them are easily overcome.

Cheeks: /* PHP Notes */

2009-06-03T17:47:58Z

PHP Notes

← Older revision		Revision as of 11:47, 3 June 2009
Line 80:		Line 80:
	** Older versions of the '''PHP-Nuke''' CMS have a bug in the calendar module. Causes infinite loop when you access the calendar. Current version of PHP-Nuke is believed to be OK.		** Older versions of the '''PHP-Nuke''' CMS have a bug in the calendar module. Causes infinite loop when you access the calendar. Current version of PHP-Nuke is believed to be OK.
	** Older versions of the '''phpWebSite''' CMS have a bug in the calendar module (completely different from the PHP-Nuke problem). Causes infinite loop when you access the calendar. Current version of phpWebSite is believed to be OK.		** Older versions of the '''phpWebSite''' CMS have a bug in the calendar module (completely different from the PHP-Nuke problem). Causes infinite loop when you access the calendar. Current version of phpWebSite is believed to be OK.

			====Perl Notes===
			If you are using the CGI::Session library, and you are using a MySQL table to store session data, the table needs to be on a MySQL 5 server. If your database is currently on mysql.swcp.com, let us know and we can move your database to mysql5.swcp.com which is our MySQL 5 server. there might be other ramifications to this if you have other code which uses MySQL. There are a few compatibility between MySQL 4 and 5, but most of them are easily overcome.

	====Apache Notes====		====Apache Notes====

Cheeks: /* PHP Notes */

2009-04-23T22:09:40Z

PHP Notes

← Older revision		Revision as of 16:09, 23 April 2009
Line 78:		Line 78:

	* '''Packages with Known Problems'''		* '''Packages with Known Problems'''
	** Older versions of the PHP-Nuke CMS have a bug in the calendar module. Causes infinite loop when you access the calendar. Current version of PHP-Nuke is believed to be OK.		** Older versions of the '''PHP-Nuke''' CMS have a bug in the calendar module. Causes infinite loop when you access the calendar. Current version of PHP-Nuke is believed to be OK.
	** Older versions of the '''phpWebSite''' CMS have a bug in the calendar module (completely different from the PHP-Nuke problem). Causes infinite loop when you access the calendar. Current version of phpWebSite is believed to be OK.		** Older versions of the '''phpWebSite''' CMS have a bug in the calendar module (completely different from the PHP-Nuke problem). Causes infinite loop when you access the calendar. Current version of phpWebSite is believed to be OK.

Cheeks: /* PHP Notes */

2009-04-23T22:09:19Z

PHP Notes

← Older revision		Revision as of 16:09, 23 April 2009
Line 77:		Line 77:
	**We strongly encourage our customers using ''Register Globals'' to consider refactoring their code at this time. ''Register Globals'' is deprecated and will be removed from PHP 6.		**We strongly encourage our customers using ''Register Globals'' to consider refactoring their code at this time. ''Register Globals'' is deprecated and will be removed from PHP 6.

			* '''Packages with Known Problems'''
			** Older versions of the PHP-Nuke CMS have a bug in the calendar module. Causes infinite loop when you access the calendar. Current version of PHP-Nuke is believed to be OK.
			** Older versions of the '''phpWebSite''' CMS have a bug in the calendar module (completely different from the PHP-Nuke problem). Causes infinite loop when you access the calendar. Current version of phpWebSite is believed to be OK.

	====Apache Notes====		====Apache Notes====

Jgentry: /* Hosting Environment Changes */

2009-04-14T23:17:39Z

Hosting Environment Changes

← Older revision		Revision as of 17:17, 14 April 2009
Line 53:		Line 53:
	<td><b>Apache Version</b></td>		<td><b>Apache Version</b></td>
	<td><b>IP Address</b></td>		<td><b>IP Address</b></td>
			<td><b>SSL  IP Address</b></td>
	</tr>		</tr>
	<tr>		<tr>

Cheeks: /* Apache Notes */

2009-04-14T18:46:19Z

Apache Notes

← Older revision		Revision as of 12:46, 14 April 2009
Line 83:		Line 83:
	**The directive "Options All" worked on the old system but will cause an error on the new system.		**The directive "Options All" worked on the old system but will cause an error on the new system.
	***Read [http://httpd.apache.org/docs/2.2/urlmapping.html#outside Apache.org's description of this directive]		***Read [http://httpd.apache.org/docs/2.2/urlmapping.html#outside Apache.org's description of this directive]

			====MySQL Notes====
			Your MySQL databases are not affected by this change. The MySQL server you are currently using is still available using the same hostname, username, and password.

			However, we do also have a newer MySQL server set up which we are working to migrate customers to. The old server (mysql.swcp.com) uses MySQL 4. The new server (mysql5.swcp.com) uses MySQL 5. If you have a database on the MySQL 4 server and would like to migrate it to the MySQL 5 server, let us know and we will copy your data to the new server.

Cheeks: /* The files you are testing */

2009-04-14T18:43:06Z

The files you are testing

← Older revision		Revision as of 12:43, 14 April 2009
Line 44:		Line 44:

	====The files you are testing====		====The files you are testing====
	The test ~~virtual~~ points at exactly the same files as your main, live site. You do not need to upload anything. Anything that you want to change can be changed through your normal file upload method (FTP), but ''be aware that this will also change your live site''.		''The test URL points at exactly the same files as your main, live site''. You do not need to upload anything. Anything that you want to change can be changed through your normal file upload method (FTP), but ''be aware that this will also change your live site''. If this presents a problem and you need to work on a '''copy''' of your web site, let us know and we will set that up.

	===Hosting Environment Changes===		===Hosting Environment Changes===

Cheeks: /* Apache Notes */

2009-04-14T18:41:09Z

Apache Notes

← Older revision		Revision as of 12:41, 14 April 2009
Line 80:		Line 80:
	*'''.htaccess files'''		*'''.htaccess files'''
	**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.		**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
	**The directive '''<code>+FollowSymLinks</code>''' needs to changed to '''<code>+SymLinksIfOwnerMatch</code>'''		**The directive '''<code>+FollowSymLinks</code>''' needs to be changed to '''<code>+SymLinksIfOwnerMatch</code>'''
			**The directive "Options All" worked on the old system but will cause an error on the new system.
	***Read [http://httpd.apache.org/docs/2.2/urlmapping.html#outside Apache.org's description of this directive]		***Read [http://httpd.apache.org/docs/2.2/urlmapping.html#outside Apache.org's description of this directive]

Cheeks: /* Hosting Environment Changes */

2009-04-14T18:39:51Z

Hosting Environment Changes

← Older revision		Revision as of 12:39, 14 April 2009
Line 59:		Line 59:
	<td>1.3</td>		<td>1.3</td>
	<td>216.184.2.18</td>		<td>216.184.2.18</td>
	<td rowspan=2>Note: SSL sites use different IP addresses.		<td rowspan=2>Note: SSL sites use<br>different IP addresses.
	</tr>		</tr>
	<tr>		<tr>

Cheeks: /* Hosting Environment Changes */

2009-04-14T18:39:37Z

Hosting Environment Changes

← Older revision		Revision as of 12:39, 14 April 2009
Line 59:		Line 59:
	<td>1.3</td>		<td>1.3</td>
	<td>216.184.2.18</td>		<td>216.184.2.18</td>
			<td rowspan=2>Note: SSL sites use different IP addresses.
	</tr>		</tr>
	<tr>		<tr>