Fellow Monasterians,
I have a content manager that I offer my customers as a "product," software if you will. The dozen or so executables are Perl scripts that fit nicely into their own directory.
To aid distribution/installation/maintenance, the idea of keeping them all in their own directory, while on a production server, is appealing. This as opposed to dumping them all into the existing cgi-bin directory that would invariably contain several completely unrelated scripts. I.e., I would like to keep all my scripts in their own directory and use a .htaccess file to make them executable.
And, while not a great benefit, it also looks more proprietary in the URL line of the browser: http://www.domain.com/acme/login.plx as opposed to http://www.domain.com/cgi-bin/login.plx
Question: What are the pros and cons of not using the standard cgi-bin directory when considering distribution, installation, maintenance, and security?
As always, thanks in advance.
In reply to Beyond style? cgi-bin vs. custom dir by bradcathey
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |