Going to have nats installed on a fresh server that has whm/cpanel on it. What I need is you to help me setup the domain/nameservers on it, and make sure the server has all the needed apps for nats. According to nats here is what they need installed. I am paying via epassporte and I Will be back from the store in about 30 minutes. ICQ me only if your serious, interested, and can do this NOW. Thanks! ICQ IN SIG
* PHP with the following support / components:
* cURL
* FreeType (with Open SSL)
* mcrypt (with blowfish & ecb support - VERY IMPORTANT)
* MySQL support (VERY IMPORTANT)
* GD support (1.8 or newer)
* PHP CLI (This needs to be the same version of php that apache is using and
must use the same php.ini file with the same settings)
* SSH Login (This must have sufficient access to the modify the document root
directory of the domain on which the NATS admin will run. We will create a
symbolic link to the nats/www directory in replacement of the current document
root directory to allow the NATS admin to be web accessible on the desired domain)
* CVS client (we cannot install NATS without this - please make sure that port 2401 is not blocked by a firewall)
* MySQL (Version 5 or Higher with NO_UNSIGNED_SUBTRACTION enabled is REQUIRED)
* Unzip (Latest Version)
* Zend Optmizer (2.6.2 or higher) or php must have "enable_dl" turned on (SEE BELOW)
* NATS Domain - Before NATS can be installed and operational on a
server, the domain that you will be using for NATS must be setup and
pointing to the NATS server. Also, Apache (main configuration and virtual
host configuration) must be set up and running on the server. If
the domain you desire to use is currently in use by something else,
please have a temporary domain in place for NATS to use during
installation and setup. Also note that NATS must operate directly on
a domain and not in a subdirectory (e.g. www.site.com is fine, but
www.site.com/nats is not acceptable) You may use 3rd level domains,
if desired (e.g. - nats.domain.com, instead of www.domain.com)
* Please remove any server admin software! If NATS is installed and
any server administration software is present we cannot guarantee NATS
will work as intended. In order to prevent any potential issues with
server admin softare, we strongly recommend removing that software from the
server prior to installing NATS. While this does not guarantee that
there will or will not be problems between NATS and your server admin
software, it should be noted that we cannot support any issues resulting
from that interaction.
* For numerous reasons, NATS will not be installed on a shared server. Performance
issues, load issues, permissions issues, and directory restriction issues are
just some of the potential reasons why it has been determined that NATS installations
on a shared server cannot realistically be done. It's also common that shared servers
will use control panel programs and/or have too many restrictions on functionality to
operate properly or predictably.
* cURL
* FreeType (with Open SSL)
* mcrypt (with blowfish & ecb support - VERY IMPORTANT)
* MySQL support (VERY IMPORTANT)
* GD support (1.8 or newer)
* PHP CLI (This needs to be the same version of php that apache is using and
must use the same php.ini file with the same settings)
* SSH Login (This must have sufficient access to the modify the document root
directory of the domain on which the NATS admin will run. We will create a
symbolic link to the nats/www directory in replacement of the current document
root directory to allow the NATS admin to be web accessible on the desired domain)
* CVS client (we cannot install NATS without this - please make sure that port 2401 is not blocked by a firewall)
* MySQL (Version 5 or Higher with NO_UNSIGNED_SUBTRACTION enabled is REQUIRED)
* Unzip (Latest Version)
* Zend Optmizer (2.6.2 or higher) or php must have "enable_dl" turned on (SEE BELOW)
* NATS Domain - Before NATS can be installed and operational on a
server, the domain that you will be using for NATS must be setup and
pointing to the NATS server. Also, Apache (main configuration and virtual
host configuration) must be set up and running on the server. If
the domain you desire to use is currently in use by something else,
please have a temporary domain in place for NATS to use during
installation and setup. Also note that NATS must operate directly on
a domain and not in a subdirectory (e.g. www.site.com is fine, but
www.site.com/nats is not acceptable) You may use 3rd level domains,
if desired (e.g. - nats.domain.com, instead of www.domain.com)
* Please remove any server admin software! If NATS is installed and
any server administration software is present we cannot guarantee NATS
will work as intended. In order to prevent any potential issues with
server admin softare, we strongly recommend removing that software from the
server prior to installing NATS. While this does not guarantee that
there will or will not be problems between NATS and your server admin
software, it should be noted that we cannot support any issues resulting
from that interaction.
* For numerous reasons, NATS will not be installed on a shared server. Performance
issues, load issues, permissions issues, and directory restriction issues are
just some of the potential reasons why it has been determined that NATS installations
on a shared server cannot realistically be done. It's also common that shared servers
will use control panel programs and/or have too many restrictions on functionality to
operate properly or predictably.
Comment