|laziness, impatience, and hubris|
I have tried IndigoPerl on Win98 and it runs great. It's excellent for testing cgi scripts and 'mock' websites. It is also excellent for newbies, like myself, as well as for seasoned veterans, who want to learn more about perl, cgi, and real servers.
Right off the bat, after you 'start apache', you have a fully functional, fully configurable Apache server with perl/mod_perl running on localhost.
Also included is the 'PerlConsole' which basically runs Apache on localhost:444 and brings up a framed browser window, with the documentation, a search for the documentation, and the package manger, which is pretty nifty.
The documentation regarding indigoperl specifics is a little thin, but what else do you really need besides perl pod.
I wouldn't reccoment anyone run this as a 'live'(on the net) server on a Win9x machine. Please get an os with more 'security' built-in.
I give this product an overall rating of ******** + 1/4* (8.25 stars).
Setup: ********* (10 stars) updated (01/10/2001)
All you need to do is download the zip, unzip, run setup.bat and reboot, that simple. Then simply go to your start menu > programs > IndigoPerl > start apache, open a browser and type http://localhost/ and do a little dance. If you wanna run it as a service(NT only) it is a bit more complicated. I personally have not tried it.
Overall Performance: ******* (7 stars)
Documentation: ********* (9 stars)
Features: ******* (7 stars)
GPM is a CGI front-end for the DPM(Dynamic Package Manager), which is a batch script with embedded perl. The GPM is very good, but lacks some important functionality and is kind of slow, and not quite robust.
There is on key thing to remember before you can successfully use it:
The handling of multiple module 2 install/download is pretty much the big bug and unimplement feature. While it appears that there is a check in place for this, it doesn't work very well and can cause some funky results(zombies).
Also when installing/downloading a module, GPM will try and parse the module, and automatically update the html version of the pod in html/lib/$Package/$Module.html, much like ActivePerls PPM(Perl Package manager).
One feature, which you can probably hack, is the unneccessary automatic updating of the repository packages list for the selected repository, every single time you visit the GPM. For example if you select http://www.indigostar.com/packages/perl5_6 as your repository, and click select, the list will be updated. And if you then chose to download/install a module, and that happens, and you get a message saying installed/downloaded click here to go back to the GPM, when you click to go back, the GPM will automatically update the list, for which there is no real reason to.
Another behaviour is to refresh the page automatically when downloading/installing a module, with updated status, which can get ridiculous when you're downloading/installing a big module like TK(1.4+MB), and causes the script to run hella slow. And when you get tired of it refreshing every 5 seconds, with little or no progress, and hit escape, or click stop on your browser, guess what happens. That's right, the module doesn't get installed/downloaded and some zombies might get created.
The good news is that dpm keeps a cache of each session in dbmcache and that bigass module'll be there if it downloaded correctly, and what might simply be the case is that the parsing/generation of the htmlpod was all you stopped. The zombies will go away once you 'stop apache'.
Another bug(appears to be) is the failure of automatic creation of a local_repository directory. There is a file called save_location.txt with local_repository as the default directory to save in, but as i said before, you have to manually create the directory. The file will be updated when you enter the full path of the directory in the GPM save to field, or whenever you edit it.
In conclusion IndigoPerl is a little funky, but hella cool %-)
"cRaZy is co01, but sometimes cRaZy is cRaZy".