SWCP Support Wiki - User contributions [en]

Migration to Web Farm 2 from NMIA Web Server

2009-04-15T18:27:53Z

Jgentry: /* Apache Notes */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current server, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the NMIA Web Server
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc"><b>
<td> </td>
<td>IP Address</td>
<td>PHP<br />Version</td>
<td>suPHP<br />Available?</td>
<td>Apache<br />Version</td>
<td>Supports<br />SSL?</td>
</b></tr>
<tr>
<td bgcolor="#cccccc">Current Server</td>
<td>64.42.128.55  or<br />64.42.142.0/22</td>
<td>4.4</td>
<td>No</td>
<td>1.3</td>
<td>No</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>216.184.2.32</td>
<td>5.2</td>
<td>Yes</td>
<td>2.2</td>
<td>Yes</td>
</tr>
</table>
<br />

====PHP Notes====
*'''SuPHP'''
**The SWCP Web Farm enables SuPHP by default. While we can disable it for your site upon request, we strongly encourage you to take advantage of this security enhancement.
**The transition to SuPHP may require a one-time file permissions change for files that were created by Apache on the current server.
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**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.
**Questions? Please read [http://us.php.net/register_globals PHP.net's thorough description of ''Register Globals.'']

====CGI Notes====
CGI changes are probably the most significant, with the greatest potential for confusion.
*'''cgiwrap'''
**Your cgiwrap scripts will <b>not</b> work if you reference them using 'www.nmia.com.' For example, this form would not submit to the new Web Farm:
***<code><form <nowiki>action="http://</nowiki><b>www.nmia.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Your cgiwrap scripts <b>will</b> work if you used relative URL's or your domain name. Both of these forms would submit as desired:
***<code><form <nowiki>action="/cgi-bin/cgiwrap/Username/SomeScript.pl"...</nowiki></code>
***<code><form <nowiki>action="http://</nowiki><b>www.YourDomain.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Gory details for those who care:
***The Web Farm uses suEXEC rather than cgiwrap. We emulate the behavior of cgiwrap by adding an Apache ScriptAlias for your virtual:
****<code> Name=/cgi-bin/cgiwrap/Username/ Path=/users/Username/public_html/cgi-bin/</code>
****If you're changing your code anyway, we can change this ScriptAlias something a little nicer. Just let us know.
*'''formmail'''
**NMIA's 'formmail' script will continue to work as before. However, we do encourage you to consider using the [[mfrwc|SWCP Email Form Responder with Captcha]] to reduce the amount of Spam you receive.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

====Web Hits Reports====
*'''Web Trends'''
**We will be replacing the Web Trends log analysis report with Webalizer.

Migration to Web Farm 2 from NMIA Web Server

2009-04-15T18:26:46Z

Jgentry: /* CGI Notes */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current server, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the NMIA Web Server
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc"><b>
<td> </td>
<td>IP Address</td>
<td>PHP<br />Version</td>
<td>suPHP<br />Available?</td>
<td>Apache<br />Version</td>
<td>Supports<br />SSL?</td>
</b></tr>
<tr>
<td bgcolor="#cccccc">Current Server</td>
<td>64.42.128.55  or<br />64.42.142.0/22</td>
<td>4.4</td>
<td>No</td>
<td>1.3</td>
<td>No</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>216.184.2.32</td>
<td>5.2</td>
<td>Yes</td>
<td>2.2</td>
<td>Yes</td>
</tr>
</table>
<br />

====PHP Notes====
*'''SuPHP'''
**The SWCP Web Farm enables SuPHP by default. While we can disable it for your site upon request, we strongly encourage you to take advantage of this security enhancement.
**The transition to SuPHP may require a one-time file permissions change for files that were created by Apache on the current server.
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**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.
**Questions? Please read [http://us.php.net/register_globals PHP.net's thorough description of ''Register Globals.'']

====CGI Notes====
CGI changes are probably the most significant, with the greatest potential for confusion.
*'''cgiwrap'''
**Your cgiwrap scripts will <b>not</b> work if you reference them using 'www.nmia.com.' For example, this form would not submit to the new Web Farm:
***<code><form <nowiki>action="http://</nowiki><b>www.nmia.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Your cgiwrap scripts <b>will</b> work if you used relative URL's or your domain name. Both of these forms would submit as desired:
***<code><form <nowiki>action="/cgi-bin/cgiwrap/Username/SomeScript.pl"...</nowiki></code>
***<code><form <nowiki>action="http://</nowiki><b>www.YourDomain.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Gory details for those who care:
***The Web Farm uses suEXEC rather than cgiwrap. We emulate the behavior of cgiwrap by adding an Apache ScriptAlias for your virtual:
****<code> Name=/cgi-bin/cgiwrap/Username/ Path=/users/Username/public_html/cgi-bin/</code>
****If you're changing your code anyway, we can change this ScriptAlias something a little nicer. Just let us know.
*'''formmail'''
**NMIA's 'formmail' script will continue to work as before. However, we do encourage you to consider using the [[mfrwc|SWCP Email Form Responder with Captcha]] to reduce the amount of Spam you receive.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

====Web Hits Reports====
*'''Web Trends'''
**We will be replacing the Web Trends log analysis report with Webalizer.

Migration to Web Farm 2 from NMIA Web Server

2009-04-15T18:25:26Z

Jgentry: /* Web Hits Reports */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current server, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the NMIA Web Server
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc"><b>
<td> </td>
<td>IP Address</td>
<td>PHP<br />Version</td>
<td>suPHP<br />Available?</td>
<td>Apache<br />Version</td>
<td>Supports<br />SSL?</td>
</b></tr>
<tr>
<td bgcolor="#cccccc">Current Server</td>
<td>64.42.128.55  or<br />64.42.142.0/22</td>
<td>4.4</td>
<td>No</td>
<td>1.3</td>
<td>No</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>216.184.2.32</td>
<td>5.2</td>
<td>Yes</td>
<td>2.2</td>
<td>Yes</td>
</tr>
</table>
<br />

====PHP Notes====
*'''SuPHP'''
**The SWCP Web Farm enables SuPHP by default. While we can disable it for your site upon request, we strongly encourage you to take advantage of this security enhancement.
**The transition to SuPHP may require a one-time file permissions change for files that were created by Apache on the current server.
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**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.
**Questions? Please read [http://us.php.net/register_globals PHP.net's thorough description of ''Register Globals.'']

====CGI Notes====
CGI changes are probably the most significant, with the greatest potential for confusion.
*'''cgiwrap'''
**Your cgiwrap scripts will <b>not</b> work if you reference them using 'www.nmia.com.' For example, this form would not submit to the new servers:
***<code><form <nowiki>action="http://</nowiki><b>www.nmia.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Your cgiwrap scripts <b>will</b> work if you used relative URL's or your domain name. Both of these forms would submit as desired:
***<code><form <nowiki>action="/cgi-bin/cgiwrap/Username/SomeScript.pl"...</nowiki></code>
***<code><form <nowiki>action="http://</nowiki><b>www.YourDomain.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Gory details for those who care:
***The Web Farm uses suEXEC rather than cgiwrap. We emulate the behavior of cgiwrap by adding an Apache ScriptAlias for your virtual:
****<code> Name=/cgi-bin/cgiwrap/Username/ Path=/users/Username/public_html/cgi-bin/</code>
****If you're changing your code anyway, we can change this ScriptAlias something a little nicer. Just let us know.
*'''formmail'''
**NMIA's 'formmail' script will continue to work as before. However, we do encourage you to consider using the [[mfrwc|SWCP Email Form Responder with Captcha]] to reduce the amount of Spam you receive.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

====Web Hits Reports====
*'''Web Trends'''
**We will be replacing the Web Trends log analysis report with Webalizer.

Migration to Web Farm 2 from NMIA Web Server

2009-04-15T00:44:52Z

Jgentry:

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current server, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the NMIA Web Server
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc"><b>
<td> </td>
<td>IP Address</td>
<td>PHP<br />Version</td>
<td>suPHP<br />Available?</td>
<td>Apache<br />Version</td>
<td>Supports<br />SSL?</td>
</b></tr>
<tr>
<td bgcolor="#cccccc">Current Server</td>
<td>64.42.128.55  or<br />64.42.142.0/22</td>
<td>4.4</td>
<td>No</td>
<td>1.3</td>
<td>No</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>216.184.2.32</td>
<td>5.2</td>
<td>Yes</td>
<td>2.2</td>
<td>Yes</td>
</tr>
</table>
<br />

====PHP Notes====
*'''SuPHP'''
**The SWCP Web Farm enables SuPHP by default. While we can disable it for your site upon request, we strongly encourage you to take advantage of this security enhancement.
**The transition to SuPHP may require a one-time file permissions change for files that were created by Apache on the current server.
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**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.
**Questions? Please read [http://us.php.net/register_globals PHP.net's thorough description of ''Register Globals.'']

====CGI Notes====
CGI changes are probably the most significant, with the greatest potential for confusion.
*'''cgiwrap'''
**Your cgiwrap scripts will <b>not</b> work if you reference them using 'www.nmia.com.' For example, this form would not submit to the new servers:
***<code><form <nowiki>action="http://</nowiki><b>www.nmia.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Your cgiwrap scripts <b>will</b> work if you used relative URL's or your domain name. Both of these forms would submit as desired:
***<code><form <nowiki>action="/cgi-bin/cgiwrap/Username/SomeScript.pl"...</nowiki></code>
***<code><form <nowiki>action="http://</nowiki><b>www.YourDomain.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Gory details for those who care:
***The Web Farm uses suEXEC rather than cgiwrap. We emulate the behavior of cgiwrap by adding an Apache ScriptAlias for your virtual:
****<code> Name=/cgi-bin/cgiwrap/Username/ Path=/users/Username/public_html/cgi-bin/</code>
****If you're changing your code anyway, we can change this ScriptAlias something a little nicer. Just let us know.
*'''formmail'''
**NMIA's 'formmail' script will continue to work as before. However, we do encourage you to consider using the [[mfrwc|SWCP Email Form Responder with Captcha]] to reduce the amount of Spam you receive.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

====Web Hits Reports====
FIX ME!!!!

Migration to Web Farm 2 from NMIA Web Server

2009-04-15T00:43:47Z

Jgentry: /* CGI Notes */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current server, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the NMIA Web Server
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc"><b>
<td> </td>
<td>IP Address</td>
<td>PHP<br />Version</td>
<td>suPHP<br />Available?</td>
<td>Apache<br />Version</td>
<td>Supports<br />SSL?</td>
</b></tr>
<tr>
<td bgcolor="#cccccc">Current Server</td>
<td>64.42.128.55  or<br />64.42.142.0/22</td>
<td>4.4</td>
<td>No</td>
<td>1.3</td>
<td>No</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>216.184.2.32</td>
<td>5.2</td>
<td>Yes</td>
<td>2.2</td>
<td>Yes</td>
</tr>
</table>
<br />

====PHP Notes====
*'''SuPHP'''
**The SWCP Web Farm enables SuPHP by default. While we can disable it for your site upon request, we strongly encourage you to take advantage of this security enhancement.
**The transition to SuPHP may require a one-time file permissions change for files that were created by Apache on the current server.
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**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.
**Questions? Please read [http://us.php.net/register_globals PHP.net's thorough description of ''Register Globals.'']

====CGI Notes====
CGI changes are probably the most significant, with the greatest potential for confusion.
*'''cgiwrap'''
**Your cgiwrap scripts will <b>not</b> work if you reference them using 'www.nmia.com.' For example, this form would not submit to the new servers:
***<code><form <nowiki>action="http://</nowiki><b>www.nmia.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Your cgiwrap scripts <b>will</b> work if you used relative URL's or your domain name. Both of these forms would submit as desired:
***<code><form <nowiki>action="/cgi-bin/cgiwrap/Username/SomeScript.pl"...</nowiki></code>
***<code><form <nowiki>action="http://</nowiki><b>www.YourDomain.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Gory details for those who care:
***The Web Farm uses suEXEC rather than cgiwrap. We emulate the behavior of cgiwrap by adding an Apache ScriptAlias for your virtual:
****<code> Name=/cgi-bin/cgiwrap/Username/ Path=/users/Username/public_html/cgi-bin/</code>
****If you're changing your code anyway, we can change this ScriptAlias something a little nicer. Just let us know.
*'''formmail'''
**NMIA's 'formmail' script will continue to work as before. However, we do encourage you to consider using the [[mfrwc|SWCP Email Form Responder with Captcha]] to reduce the amount of Spam you receive.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

Migration to Web Farm 2 from NMIA Web Server

2009-04-15T00:41:55Z

Jgentry: /* CGI Notes */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current server, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the NMIA Web Server
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc"><b>
<td> </td>
<td>IP Address</td>
<td>PHP<br />Version</td>
<td>suPHP<br />Available?</td>
<td>Apache<br />Version</td>
<td>Supports<br />SSL?</td>
</b></tr>
<tr>
<td bgcolor="#cccccc">Current Server</td>
<td>64.42.128.55  or<br />64.42.142.0/22</td>
<td>4.4</td>
<td>No</td>
<td>1.3</td>
<td>No</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>216.184.2.32</td>
<td>5.2</td>
<td>Yes</td>
<td>2.2</td>
<td>Yes</td>
</tr>
</table>
<br />

====PHP Notes====
*'''SuPHP'''
**The SWCP Web Farm enables SuPHP by default. While we can disable it for your site upon request, we strongly encourage you to take advantage of this security enhancement.
**The transition to SuPHP may require a one-time file permissions change for files that were created by Apache on the current server.
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**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.
**Questions? Please read [http://us.php.net/register_globals PHP.net's thorough description of ''Register Globals.'']

====CGI Notes====
CGI changes are probably the most significant, with the greatest potential for confusion.
*'''cgiwrap'''
**Your cgiwrap scripts will <b>not</b> work if you reference them using 'www.nmia.com.' For example, this form would not submit to the new servers:
***<code><form <nowiki>action="http://</nowiki><b>www.nmia.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Your cgiwrap scripts <b>will</b> work if you used relative URL's or your domain name. Both of these forms would submit as desired:
***<code><form <nowiki>action="/cgi-bin/cgiwrap/Username/SomeScript.pl"...</nowiki></code>
***<code><form <nowiki>action="http://</nowiki><b>www.YourDomain.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Gory details for those who care:
***The Web Farm uses suEXEC rather than cgiwrap. We emulate the behavior of cgiwrap by adding an Apache ScriptAlias for your virtual:
****<code> Name=/cgi-bin/cgiwrap/Username/ Path=/users/Username/public_html/cgi-bin/</code>
****If you're changing your code anyway, we can change this ScriptAlias something a little nicer. Just let us know.
*'''formmail'''
**NMIA's 'formmail' script will continue to work as before. However, we do encourage you to consider using the [[SWCP Web Farm email script|Email Form Responder with Captcha]], which uses Captcha to reduce Spam.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

Migration to Web Farm 2 from NMIA Web Server

2009-04-15T00:39:31Z

Jgentry: /* CGI Notes */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current server, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the NMIA Web Server
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc"><b>
<td> </td>
<td>IP Address</td>
<td>PHP<br />Version</td>
<td>suPHP<br />Available?</td>
<td>Apache<br />Version</td>
<td>Supports<br />SSL?</td>
</b></tr>
<tr>
<td bgcolor="#cccccc">Current Server</td>
<td>64.42.128.55  or<br />64.42.142.0/22</td>
<td>4.4</td>
<td>No</td>
<td>1.3</td>
<td>No</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>216.184.2.32</td>
<td>5.2</td>
<td>Yes</td>
<td>2.2</td>
<td>Yes</td>
</tr>
</table>
<br />

====PHP Notes====
*'''SuPHP'''
**The SWCP Web Farm enables SuPHP by default. While we can disable it for your site upon request, we strongly encourage you to take advantage of this security enhancement.
**The transition to SuPHP may require a one-time file permissions change for files that were created by Apache on the current server.
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**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.
**Questions? Please read [http://us.php.net/register_globals PHP.net's thorough description of ''Register Globals.'']

====CGI Notes====
CGI changes are probably the most significant, with the greatest potential for confusion.
*'''cgiwrap'''
**Your cgiwrap scripts will <b>not</b> work if you reference them using 'www.nmia.com.' For example, this form would not submit to the new servers:
***<code><form <nowiki>action="http://</nowiki><b>www.nmia.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Your cgiwrap scripts <b>will</b> work if you used relative URL's or your domain name. Both of these forms would submit as desired:
***<code><form <nowiki>action="/cgi-bin/cgiwrap/Username/SomeScript.pl"...</nowiki></code>
***<code><form <nowiki>action="http://</nowiki><b>www.YourDomain.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Gory details for those who care:
***The Web Farm uses suEXEC rather than cgiwrap. We emulate the behavior of cgiwrap by adding an Apache ScriptAlias for your virtual:
****<code> Name=/cgi-bin/cgiwrap/Username/ Path=/users/Username/public_html/cgi-bin/</code>
****If you're changing your code anyway, we can change this ScriptAlias something a little nicer. Just let us know.
*'''formmail'''
**NMIA's 'formmail' script will continue to work as before. However, we do encourage you to consider using the SWCP Web Farm email script, which uses Captcha to reduce Spam.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

Migration to Web Farm 2 from NMIA Web Server

2009-04-15T00:38:32Z

Jgentry:

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current server, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the NMIA Web Server
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc"><b>
<td> </td>
<td>IP Address</td>
<td>PHP<br />Version</td>
<td>suPHP<br />Available?</td>
<td>Apache<br />Version</td>
<td>Supports<br />SSL?</td>
</b></tr>
<tr>
<td bgcolor="#cccccc">Current Server</td>
<td>64.42.128.55  or<br />64.42.142.0/22</td>
<td>4.4</td>
<td>No</td>
<td>1.3</td>
<td>No</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>216.184.2.32</td>
<td>5.2</td>
<td>Yes</td>
<td>2.2</td>
<td>Yes</td>
</tr>
</table>
<br />

====PHP Notes====
*'''SuPHP'''
**The SWCP Web Farm enables SuPHP by default. While we can disable it for your site upon request, we strongly encourage you to take advantage of this security enhancement.
**The transition to SuPHP may require a one-time file permissions change for files that were created by Apache on the current server.
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**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.
**Questions? Please read [http://us.php.net/register_globals PHP.net's thorough description of ''Register Globals.'']

====CGI Notes====
CGI changes are probably the most significant, with the greatest potential for confusion.
*'''cgiwrap'''
**Your cgiwrap scripts will <b>not</b> work if you reference them using 'www.nmia.com.' For example, this form would not submit to the new servers:
***<code><form <nowiki>action="http://</nowiki><b>www.nmia.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Your cgiwrap scripts <b>will</b> work if you used relative URL's or your domain name. Both of these forms would submit as desired:
***<code><form <nowiki>action="/cgi-bin/cgiwrap/Username/SomeScript.pl"...</nowiki></code>
***<code><form <nowiki>action="http://</nowiki><b>www.MyDomain.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Gory details for those who care:
***The Web Farm uses suEXEC rather than cgiwrap. We emulate the behavior of cgiwrap by adding an Apache ScriptAlias for your virtual:
****<code> Name=/cgi-bin/cgiwrap/Username/ Path=/users/Username/public_html/cgi-bin/</code>
****If you're changing your code anyway, we can change this ScriptAlias something a little nicer. Just let us know.
*'''formmail'''
**NMIA's 'formmail' script will continue to work as before. However, we do encourage you to consider using the SWCP Web Farm email script, which uses Captcha to reduce Spam.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

Migration to Web Farm 2 from NMIA Web Server

2009-04-15T00:36:31Z

Jgentry: /* Hosting Environment Changes */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current server, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the current webfarm
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc"><b>
<td> </td>
<td>IP Address</td>
<td>PHP<br />Version</td>
<td>suPHP<br />Available?</td>
<td>Apache<br />Version</td>
<td>Supports<br />SSL?</td>
</b></tr>
<tr>
<td bgcolor="#cccccc">Current Server</td>
<td>64.42.128.55  or<br />64.42.142.0/22</td>
<td>4.4</td>
<td>No</td>
<td>1.3</td>
<td>No</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>216.184.2.32</td>
<td>5.2</td>
<td>Yes</td>
<td>2.2</td>
<td>Yes</td>
</tr>
</table>
<br />

====PHP Notes====
*'''SuPHP'''
**The SWCP Web Farm enables SuPHP by default. While we can disable it for your site upon request, we strongly encourage you to take advantage of this security enhancement.
**The transition to SuPHP may require a one-time file permissions change for files that were created by Apache on the current server.
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**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.
**Questions? Please read [http://us.php.net/register_globals PHP.net's thorough description of ''Register Globals.'']

====CGI Notes====
CGI changes are probably the most significant, with the greatest potential for confusion.
*'''cgiwrap'''
**Your cgiwrap scripts will <b>not</b> work if you reference them using 'www.nmia.com.' For example, this form would not submit to the new servers:
***<code><form <nowiki>action="http://</nowiki><b>www.nmia.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Your cgiwrap scripts <b>will</b> work if you used relative URL's or your domain name. Both of these forms would submit as desired:
***<code><form <nowiki>action="/cgi-bin/cgiwrap/Username/SomeScript.pl"...</nowiki></code>
***<code><form <nowiki>action="http://</nowiki><b>www.MyDomain.com</b>/cgi-bin/cgiwrap/Username/SomeScript.pl"...</code>
**Gory details for those who care:
***The Web Farm uses suEXEC rather than cgiwrap. We emulate the behavior of cgiwrap by adding an Apache ScriptAlias for your virtual:
****<code> Name=/cgi-bin/cgiwrap/Username/ Path=/users/Username/public_html/cgi-bin/</code>
****If you're changing your code anyway, we can change this ScriptAlias something a little nicer. Just let us know.
*'''formmail'''
**NMIA's 'formmail' script will continue to work as before. However, we do encourage you to consider using the SWCP Web Farm email script, which uses Captcha to reduce Spam.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

Migration to Web Farm 2 from NMIA Web Server

2009-04-14T23:54:02Z

Jgentry: /* Hosting Environment Changes */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current server, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the current webfarm
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc"><b>
<td> </td>
<td>IP Address</td>
<td>PHP<br />Version</td>
<td>suPHP<br />Available?</td>
<td>Apache<br />Version</td>
<td>Supports SSL?</td>
</b></tr>
<tr>
<td bgcolor="#cccccc">Current Server</td>
<td>64.42.128.55  or<br />64.42.142.0/22</td>
<td>4.4</td>
<td>No</td>
<td>1.3</td>
<td>No</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>216.184.2.32</td>
<td>5.2</td>
<td>Yes</td>
<td>2.2</td>
<td>Yes</td>
</tr>
</table>
<br />

====PHP Notes====
*'''SuPHP'''
**The SWCP Web Farm enables SuPHP by default. While we can disable it for your site upon request, we strongly encourage you to take advantage of this security enhancement.
**The transition to SuPHP may require a one-time file permissions change for files that were created by Apache on the current server.
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**Questions? Please read [http://us.php.net/register_globals PHP.net's description of ''Register Globals.'']
**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.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

Migration to Web Farm 2 from NMIA Web Server

2009-04-14T23:52:58Z

Jgentry: /* Hosting Environment Changes */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current server, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the current webfarm
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc"><b>
<td>IP Address</td>
<td> </td>
<td>PHP<br />Version</td>
<td>suPHP<br />Available?</td>
<td>Apache<br />Version</td>
<td>Supports SSL?</td>
</b></tr>
<tr>
<td bgcolor="#cccccc">Current Server</td>
<td>64.42.128.55  or<br />64.42.142.0/22</td>
<td>4.4</td>
<td>No</td>
<td>1.3</td>
<td>No</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>216.184.2.32</td>
<td>5.2</td>
<td>Yes</td>
<td>2.2</td>
<td>Yes</td>
</tr>
</table>
<br />

====PHP Notes====
*'''SuPHP'''
**The SWCP Web Farm enables SuPHP by default. While we can disable it for your site upon request, we strongly encourage you to take advantage of this security enhancement.
**The transition to SuPHP may require a one-time file permissions change for files that were created by Apache on the current server.
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**Questions? Please read [http://us.php.net/register_globals PHP.net's description of ''Register Globals.'']
**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.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

Migration to Web Farm 2 from NMIA Web Server

2009-04-14T23:33:54Z

Jgentry: /* Hosting Environment Changes */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current server, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the current webfarm
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc">
<td> </td>
<td><b>PHP Version</b></td>
<td><b>suPHP Available</b></td>
<td><b>Apache Version</b></td>
<td><b>IP Address</b></td>
</tr>
<tr>
<td bgcolor="#cccccc">Current Server</td>
<td>4.4</td>
<td>No</td>
<td>1.3</td>
<td>64.42.128.55  or 64.42.142.0/22</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>5.2</td>
<td>Yes</td>
<td>2.2</td>
<td>216.184.2.32</td>
</tr>
</table>
<br />

====PHP Notes====
*'''SuPHP'''
**The SWCP Web Farm enables SuPHP by default. While we can disable it for your site upon request, we strongly encourage you to take advantage of this security enhancement.
**The transition to SuPHP may require a one-time file permissions change for files that were created by Apache on the current server.
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**Questions? Please read [http://us.php.net/register_globals PHP.net's description of ''Register Globals.'']
**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.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

Migration to Web Farm 2 from NMIA Web Server

2009-04-14T23:31:50Z

Jgentry: /* Hosting Environment Changes */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current server, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the current webfarm
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc">
<td> </td>
<td><b>PHP Version</b></td>
<td><b>Apache Version</b></td>
<td><b>IP Address</b></td>
</tr>
<tr>
<td bgcolor="#cccccc">Current Server</td>
<td>4.4</td>
<td>1.3</td>
<td>64.42.128.55  or 64.42.142.0/22</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>5.2</td>
<td>2.2</td>
<td>216.184.2.32</td>
</tr>
</table>
<br />

====PHP Notes====
*'''SuPHP'''
**The SWCP Web Farm enables SuPHP by default. While we can disable it for your site upon request, we strongly encourage you to take advantage of this security enhancement.
**The transition to SuPHP may require a one-time file permissions change for files that were created by Apache on the current server.
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**Questions? Please read [http://us.php.net/register_globals PHP.net's description of ''Register Globals.'']
**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.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

Migration to Web Farm 2 from NMIA Web Server

2009-04-14T23:29:33Z

Jgentry: /* What to test */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current server, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the current webfarm
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc">
<td> </td>
<td><b>PHP Version</b></td>
<td><b>Apache Version</b></td>
<td><b>IP Address</b></td>
</tr>
<tr>
<td bgcolor="#cccccc">Current Webfarm</td>
<td>4.3</td>
<td>1.3</td>
<td>64.42.128.55  or 64.42.142.0/22</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>5.2</td>
<td>2.2</td>
<td>216.184.2.32</td>
</tr>
</table>
<br />

====PHP Notes====
*'''SuPHP'''
**The SWCP Web Farm enables SuPHP by default. While we can disable it for your site upon request, we strongly encourage you to take advantage of this security enhancement.
**The transition to SuPHP may require a one-time file permissions change for files that were created by Apache on the current server.
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**Questions? Please read [http://us.php.net/register_globals PHP.net's description of ''Register Globals.'']
**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.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

Migration to Web Farm 2 from NMIA Web Server

2009-04-14T23:28:50Z

Jgentry: /* MySQL Notes */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current webfarm, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the current webfarm
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc">
<td> </td>
<td><b>PHP Version</b></td>
<td><b>Apache Version</b></td>
<td><b>IP Address</b></td>
</tr>
<tr>
<td bgcolor="#cccccc">Current Webfarm</td>
<td>4.3</td>
<td>1.3</td>
<td>64.42.128.55  or 64.42.142.0/22</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>5.2</td>
<td>2.2</td>
<td>216.184.2.32</td>
</tr>
</table>
<br />

====PHP Notes====
*'''SuPHP'''
**The SWCP Web Farm enables SuPHP by default. While we can disable it for your site upon request, we strongly encourage you to take advantage of this security enhancement.
**The transition to SuPHP may require a one-time file permissions change for files that were created by Apache on the current server.
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**Questions? Please read [http://us.php.net/register_globals PHP.net's description of ''Register Globals.'']
**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.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

Migration to Web Farm 2 from NMIA Web Server

2009-04-14T23:27:28Z

Jgentry: /* PHP Notes */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current webfarm, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the current webfarm
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc">
<td> </td>
<td><b>PHP Version</b></td>
<td><b>Apache Version</b></td>
<td><b>IP Address</b></td>
</tr>
<tr>
<td bgcolor="#cccccc">Current Webfarm</td>
<td>4.3</td>
<td>1.3</td>
<td>64.42.128.55  or 64.42.142.0/22</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>5.2</td>
<td>2.2</td>
<td>216.184.2.32</td>
</tr>
</table>
<br />

====PHP Notes====
*'''SuPHP'''
**The SWCP Web Farm enables SuPHP by default. While we can disable it for your site upon request, we strongly encourage you to take advantage of this security enhancement.
**The transition to SuPHP may require a one-time file permissions change for files that were created by Apache on the current server.
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**Questions? Please read [http://us.php.net/register_globals PHP.net's description of ''Register Globals.'']
**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.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

====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.

Migration to Web Farm 2 from NMIA Web Server

2009-04-14T23:22:31Z

Jgentry: /* Hosting Environment Changes */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current webfarm, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the current webfarm
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc">
<td> </td>
<td><b>PHP Version</b></td>
<td><b>Apache Version</b></td>
<td><b>IP Address</b></td>
</tr>
<tr>
<td bgcolor="#cccccc">Current Webfarm</td>
<td>4.3</td>
<td>1.3</td>
<td>64.42.128.55  or 64.42.142.0/22</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>5.2</td>
<td>2.2</td>
<td>216.184.2.32</td>
</tr>
</table>
<br />

====PHP Notes====
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**Questions? Please read [http://us.php.net/register_globals PHP.net's description of ''Register Globals.'']
**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.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

====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.

Migration to Web Farm 2

2009-04-14T23:17:39Z

Jgentry: /* Hosting Environment Changes */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current webfarm, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the current webfarm
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc">
<td> </td>
<td><b>PHP Version</b></td>
<td><b>Apache Version</b></td>
<td><b>IP Address</b></td>
<td><b>SSL  IP Address</b></td>
</tr>
<tr>
<td bgcolor="#cccccc">Current Webfarm</td>
<td>4.3</td>
<td>1.3</td>
<td>216.184.2.18</td>
<td rowspan=2>Note: SSL sites use<br>different IP addresses.
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>5.2</td>
<td>2.2</td>
<td>216.184.2.32</td>
</tr>
</table>
<br />

====PHP Notes====
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**Questions? Please read [http://us.php.net/register_globals PHP.net's description of ''Register Globals.'']
**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.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

====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.

Migration to Web Farm 2 from NMIA Web Server

2009-04-14T23:16:06Z

Jgentry: /* Hosting Environment Changes */

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current webfarm, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the current webfarm
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc">
<td> </td>
<td><b>PHP Version</b></td>
<td><b>Apache Version</b></td>
<td><b>IP Address</b></td>
</tr>
<tr>
<td bgcolor="#cccccc">Current Webfarm</td>
<td>4.3</td>
<td>1.3</td>
<td>216.184.2.18</td>
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>5.2</td>
<td>2.2</td>
<td>216.184.2.32</td>
</tr>
</table>
<br />

====PHP Notes====
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**Questions? Please read [http://us.php.net/register_globals PHP.net's description of ''Register Globals.'']
**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.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

====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.

Migration to Web Farm 2 from NMIA Web Server

2009-04-14T23:12:42Z

Jgentry: New page: ==Migrating Your Website to the New Southwest Cyberport Webfarm== ===Purpose=== *Describe how to test your current site on the new Webfarm *Encourage thorough testing of sites moving to t...

==Migrating Your Website to the New Southwest Cyberport Webfarm==

===Purpose===
*Describe how to test your current site on the new Webfarm
*Encourage thorough testing of sites moving to the new Southwest Cyberport Webfarm
*List the upgraded software packages
*Provide a few suggestions to avoid common pitfalls.
*Encourage '''thorough''' testing. Really. You won't regret doing it. You will probably regret ''not'' doing it.

===Testing Your Site===
====What to test====
We cannot stress enough the importance of testing your site on the new webfarm. Do not just verify that your home page loads. Here is a partial list of behavior that should receive close scrutiny:
*Form submissions
**Make sure your customers can reach you!
*Dynamic content generated by:
**PHP code
**CGI scripts
**Apache Server Side Includes
**Javascript
*Redirection [http://en.wikipedia.org/wiki/URL_redirection#Purposes (best used sparingly)]:
**.htaccess, PHP, META tags, CGI, Javascript, etc.

Beware any hard-coded links (like <a href="http://www.YourDomain.com/otherfile.html">) - those will go to the current webfarm, rather than the new one.

====Where to test====
In most cases, we want to add the subdomain 'test' so that:
:www.YourDomain.com => your site, via the current webfarm
:test.YourDomain.com => your site, via the new webfarm

*If we control DNS for your domain:
** We have already created the URL ''''test'''.YourDomain.com' - use this URL to test your current site on the new webfarm. Let us know if this URL doesn't work.
** When you're finished testing your site, [mailto:help@swcp.com send us an email] instructing us to fully migrate your site to the new webfarm.
** Test your site again, using 'www.YourDomain.com' rather than the test URL.

*If we do '''not''' control DNS for your domain:
<div style="background-color:#FFF2F2; border:red solid 2px; margin-left:1em">
:Be careful when changing DNS entries for your domain.<br />Invalid DNS entries will make it impossible to reach your site.<br />These steps may not work for domains with multiple subdomains or other non-trivial DNS records
</div>
:* For testing, we have created a URL for you to use that is similar to this:

::'''<code>test-yourdomain.swcp.com.</code>'''

:* Once you are finished testing, update all relevant '''A''' records to point to 216.184.2.32.

====The files you are testing====
''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===
<table cellpadding=4 border=1>
<tr bgcolor="#cccccc">
<td> </td>
<td><b>PHP Version</b></td>
<td><b>Apache Version</b></td>
<td><b>IP Address</b></td>
</tr>
<tr>
<td bgcolor="#cccccc">Current Webfarm</td>
<td>4.3</td>
<td>1.3</td>
<td>216.184.2.18</td>
<td rowspan=2>Note: SSL sites use<br>different IP addresses.
</tr>
<tr>
<td bgcolor="#cccccc">New Webfarm</td>
<td>5.2</td>
<td>2.2</td>
<td>216.184.2.32</td>
</tr>
</table>
<br />

====PHP Notes====
*'''Register Globals'''
**Register Globals is now '''disabled''' by default. We can enable it for your site at your request.
**Questions? Please read [http://us.php.net/register_globals PHP.net's description of ''Register Globals.'']
**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.

====Apache Notes====
*'''.htaccess files'''
**Though most .htaccess behavior will not be affected, all sites with .htaccess files should be tested.
**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]

====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.

For Web Developers

2009-04-14T23:10:03Z

Jgentry: /* Sections */

As part of SWCP's interest in Open Source software and easy to use web based applications we're working on making several open source packages easily available, see [[Webapps]] for more information about this. Many common questions are answered in the
[[KB WebApps|Web Apps]] section of our [[Knowledge Base]].

This section of the Wiki will contain more detailed information about web applications, CSS, Web brower issues,
HTML editors, and other web development issues. This is still under development, so bear with us. If you have a
topic you'd like us to cover, send email to help@swcp.com and we'll try to find you some answers.

==Sections==
[[Migration to Web Farm 2]]

[[Migration to Web Farm 2 from NMIA Web Server]]

How web browsing works. ( whose rendering what, when? )

[[Quick Recipes]] ( Short snippets of code for specific tasks )

[[Website Problems]] Things that behave badly.

[[SWCP CGI Scripts]] Scripts available for adding counters, simple forms, etc.

[[Server Side Includes]]

[[Web Hits Reports]]

Website Design Tools

Content Management Tools

[[WebApps]] - Tips and tricks for the web applications that SWCP supports (MediaWiki, WordPress, etc.)

Migration to Web Farm 2

2009-04-07T20:47:59Z

Jgentry:

Migration to Web Farm 2

2009-04-07T20:43:01Z

For Web Developers

2009-04-07T20:41:21Z

Jgentry:

As part of SWCP's interest in Open Source software and easy to use web based applications we're working on making several open source packages easily available, see [[Webapps]] for more information about this. Many common questions are answered in the
[[KB WebApps|Web Apps]] section of our [[Knowledge Base]].

This section of the Wiki will contain more detailed information about web applications, CSS, Web brower issues,
HTML editors, and other web development issues. This is still under development, so bear with us. If you have a
topic you'd like us to cover, send email to help@swcp.com and we'll try to find you some answers.

==Sections==
[[Migration to Web Farm 2]]

How web browsing works. ( whose rendering what, when? )

[[Quick Recipes]] ( Short snippets of code for specific tasks )

[[Website Problems]] Things that behave badly.

[[SWCP CGI Scripts]] Scripts available for adding counters, simple forms, etc.

[[Server Side Includes]]

Website Design Tools

Content Management Tools

[[WebApps]] - Tips and tricks for the web applications that SWCP supports (MediaWiki, WordPress, etc.)

Website Access Control

2008-09-20T22:22:12Z

Jgentry:

A web application developed by SWCP to make it easy for you to password protect a section of your website. The first page of the application are the instructions for using it. From any screen of the application, you can return to those instructions by clicking on "Access Control Home". [https://members.swcp.com/webdiracl/index.php].

Website Access Control

2008-09-20T22:21:36Z

Jgentry:

Website Access Control

2008-09-20T22:09:47Z

Jgentry: New page: A web application developed by SWCP to make it easy for you to password protect a section of your website.

A web application developed by SWCP to make it easy for you to password protect a section of your website.

Quick Recipes

2008-09-20T22:09:01Z

Jgentry:

Short snippets of code for specific web applications.

===Creating password protected web pages===
We have an online tool for building simple password protected areas that is available from the [https://members.swcp.com Members Only Area]. It's designed to be easy to use, but here are instructions for using [[Website Access Control]]. If you're curious what is needed to [[set up password protected web pages]] with a text editor, follow the link.

===Video using QuickTime===
[[Video with QuickTime]] provides an example of opening a POP-up window and viewing a QT movie.