Hi... I'm writing as to share our experiences and ideas on the packaging and the deployment of CAP on servers.
I'm using CAP for a long time now and for me is by far the best way to develop web applications. But as a freelance programmer it is quite common to have diffidence regarding the deployment of a ready application on client's servers, if their servers are not fully accessible by me (like a dedicated hosting server might be). Usually this is the most common case for not having CAP powering an application I'm creating. The problem is for the people that wish to use a shared web hostin environment. And of course Perl was always something found almost in any (Unix based) hosting environment, and from my experience cgi is quite usual to be enabled, mod_perl is not that uncommon environment and fastcgi and perperl are quite uncommon. So, even for the cgi case, I believe that the deployment of CAP on shared hosting environments can become quite difficult. Of course the case of having a working CAP in a shared hosting environment without even ssh access most of the times is prohibitive. I believe that it might be a good idea if feasible to have something (it might me some guidelines, procedures, software, don't know) that might ease the deployment. In the past I have made it to deploy a big CAP in a shared hosting environment with ssh, by installing many modules through cpan to users home directory. I can not tell that this was my best, since cpan access is not always available to user's (even when ssh access is available), incompatibilities with system modules and libraries may arrise and the scenario of moving the application to another server is troublesome. CAP is Perl and I do believe that Perl is portable, but CAPs are not easy to install or move in such environments. I've tried using PAR. I really thought that PAR would be ideal for the whole situation, since it would have self contained all the modules and the application that would ease the installation and deployment. I created all the necessary files, but the resulting packaged CAP was not working correctly giving quite strange errors. Have any of you managed to approach this problem in any effective way? I believe that a solution (any kind) that would ease the packaging and the deployment of CAP would be highly beneficial for CAP and it's users. In the ideal scenario CAP might have a helper tool, to ease the packaging and deployment of the application on servers (maybe by using PAR). There are cases where a a web server and Perl (even as cgi) is available and should be adequate for a CAP to work, but it's not. Regards, Giannis --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
