Hi Folks,
I've been trying to determine a suitable host for my site. I would like it to be hosted in the U.S as most of the traffic will eminate from there.
I had chosen WebsiteSource shared hosting package, but it looks like there may be a problem with one of the requirements needed by Actinic. I sent them the list of requirements as printed in the users guide.
They responded as follows:
This VPS account is a much more expensive package than the shared hosting, which suggests that the shared hosting doesn't have root access to the server.
A couple of questions arise from this.
1. Does Actinic actually require access to the Root Server? Not sure I fully understand the wording of the requirements above. Or that Website Source has!
2. Can any American users, or anyone else for that matter, recommend a shared hosting account based in the U.S. that works well with Actinic?
Hope someone can advise.
Many thanks.
Myles Sinclair
I've been trying to determine a suitable host for my site. I would like it to be hosted in the U.S as most of the traffic will eminate from there.
I had chosen WebsiteSource shared hosting package, but it looks like there may be a problem with one of the requirements needed by Actinic. I sent them the list of requirements as printed in the users guide.
The requirements for Actinic to run successfully are as follows:
1. A UNIX or Windows NT system running a web server.
2. The web server must support POSTs and GETs to CGI scripts implemented in Perl
3. Perl 5.004 or greater must be installed on the server
4. The user must have access to a cgi-bin directory (or any directory that allows them to execute
CGI scripts).
5. The user must have access to a web server document directory (a directory from which the
web server distributes files). This directory is referred to as the web root directory.
6. The CGI scripts must have access to the web root directory (the directory from #5).
7. The effective user ID of the CGI scripts when they are executed via the web browser must
have read and write access to the web root directory (from #5).
8. The user ID of the web server must have read access to the web root directory (from #5) and
read/execute access to the cgi-bin directory (from #4).
9. The server must execute the CGI scripts in the directory in which they are installed. (There
has never been a problem with UNIX servers or third party NT web servers violating this
requirement, but Microsoft's IIS breaks this rule unless the cgi-bin directories are located in a
particular directory specified by IIS.)
10. The user must have FTP access to the server.
11. If the user plans to FTP files to the server, their FTP account must be able to read, write, and
delete files in the cgi-bin directory and the web root directory (from #5). They must also be
able to create sub-directories in the catalog directory. Users on UNIX systems must also be
able to change the file and directory permissions.
12. Not required.
13. If the user plans to perform manual installs, they must have some method of transporting and
installing the files on the web server.
Advanced Users Guide - 85
14. A SMTP server must be available to the CGI scripts so that the user is notified via
email when new orders arrive.
15.Not required
16. If the user plans to use SSL to secure the credit card details of their customers, the catalog
files (files in the acatalog directory created within the acatalog directory from #5) must be
accessible to the secure server.
1. A UNIX or Windows NT system running a web server.
2. The web server must support POSTs and GETs to CGI scripts implemented in Perl
3. Perl 5.004 or greater must be installed on the server
4. The user must have access to a cgi-bin directory (or any directory that allows them to execute
CGI scripts).
5. The user must have access to a web server document directory (a directory from which the
web server distributes files). This directory is referred to as the web root directory.
6. The CGI scripts must have access to the web root directory (the directory from #5).
7. The effective user ID of the CGI scripts when they are executed via the web browser must
have read and write access to the web root directory (from #5).
8. The user ID of the web server must have read access to the web root directory (from #5) and
read/execute access to the cgi-bin directory (from #4).
9. The server must execute the CGI scripts in the directory in which they are installed. (There
has never been a problem with UNIX servers or third party NT web servers violating this
requirement, but Microsoft's IIS breaks this rule unless the cgi-bin directories are located in a
particular directory specified by IIS.)
10. The user must have FTP access to the server.
11. If the user plans to FTP files to the server, their FTP account must be able to read, write, and
delete files in the cgi-bin directory and the web root directory (from #5). They must also be
able to create sub-directories in the catalog directory. Users on UNIX systems must also be
able to change the file and directory permissions.
12. Not required.
13. If the user plans to perform manual installs, they must have some method of transporting and
installing the files on the web server.
Advanced Users Guide - 85
14. A SMTP server must be available to the CGI scripts so that the user is notified via
email when new orders arrive.
15.Not required
16. If the user plans to use SSL to secure the credit card details of their customers, the catalog
files (files in the acatalog directory created within the acatalog directory from #5) must be
accessible to the secure server.
https://helpdesk.websitesource.com/v...&pass=f61b4212
You can also reply to this e-mail.
Ticket Ref : 1843-TAHZ-6216
Ticket Subject : Query
Reply:
If you have a vps account you ahve root access to the vps server itself and
can install any 3rd party software, while we still be unable to install the
software for you. also all of our software we run on the non vps accounts is
listed here:
http://www.websitesource.com/company/network.shtml
You can also reply to this e-mail.
Ticket Ref : 1843-TAHZ-6216
Ticket Subject : Query
Reply:
If you have a vps account you ahve root access to the vps server itself and
can install any 3rd party software, while we still be unable to install the
software for you. also all of our software we run on the non vps accounts is
listed here:
http://www.websitesource.com/company/network.shtml
A couple of questions arise from this.
1. Does Actinic actually require access to the Root Server? Not sure I fully understand the wording of the requirements above. Or that Website Source has!
2. Can any American users, or anyone else for that matter, recommend a shared hosting account based in the U.S. that works well with Actinic?
Hope someone can advise.
Many thanks.
Myles Sinclair
Comment