Sounds to me like you're developing something that you need in various clients' hosting accounts- of their choosing.
I have experience with this. I would honestly do one of three things-
- host them yourself (rent a server, $150/$300 mo or so)
- pick the host for all your clients- questions asked, ok.. but you make the final decision.
- quit, seriously. Go find another job where management has some common sense.
We do general IT, and one of the things we do, is optionally manage client websites. I tried solving problems with installer scripts, etc etc. But after 5 sites, it gets hard... Actually, it gets messy and dangerous to your business. Things will break, and if you don't have a standard method of installation (cpan), things will break, it will be hard to update modules, clients will complain, management will complain, you will be in devhell.
Use the shell and cpan- or have the isp install the stuff- or do the hosting yourself. Otherwise you can't update the modules, can you? Sorry to go on about this, I just really think you're headed into a nightmare.
| [reply] |
Thanks for your comments. Yes - I agree there are issues when you install with whoever's ISP. But this script is already on over 1000 clients' own webservers, whoever they might be and hasn't run into any real problems. Well, none that couldn't be solved easily enough. We don't want to be doing stuff that would be site-specific, but I was expecting the CGI::Session module to be more commonly installed. Was it more recently released? The O'Reilly Perl book I have doesn't cover it, though it covers the rest of the CGI module. (book was rev. 2000)
| [reply] |