|P is for Practical|
Re: Perl/CGI Development on Win32 in 2004by Anneq (Vicar)
|on Aug 17, 2004 at 19:05 UTC||Need Help??|
I am developing Perl/CGI on Win32 and publishing to a remote unix server. I use cvs (version control) with Eclipse (IDE) and EPIC (Eclipse plugin for Perl). Locally, I use Apache for my web server. This is all open source and all excellent stuff.
Before Eclipse, I was making changes locally using gVim (IDE) and then using SSH to upload the modified files. Very time consuming. After trying out cvs, and in particular, Eclipse, I don't know how I got by without it.
Basically I set up a cvs repository on the remote server. cvs and Eclipse both support SSH. My local web source directoy (on my laptop) is a cvs workspace that was created by checking out a copy from the repository. Once I've made my changes locally and am satisfied with the changes, I commit those changes to the remote cvs repository. My remote production web source, is also a cvs workspace that was created by checking it out from the repository. Now it only takes a single cvs update command to update this remote workspace from the repository. One command brings the entire remote web source up to date. Its a lot faster and less error prone then doing it manually.
It takes a little while to get everything set up initially but after that is is extremely easy to use and makes development much more efficient. I can also roll-back to previous versions if I decide that I don't like the latest changes I've made
To add icing to the cake, Eclipse has numerous other powerful plugins. I think that the things you find lacking in Open Perl IDE, you'll find are supported by Eclipse. I tried Open Perl IDE and it didn't have what I was looking for. As well, I was concerned that it didn't seem to have anyone currently working on improving it.
I use SQLite for my database locally, which is also supported on the remote host. I haven't had any problems with it. It even has some free management tools for Win32, such as SQLite Database Browser.
Not what you were asking but, FWIW, Perl modules/tools that I find essential are Template Toolkit, CGI, CGI::Application, CGI::Session, DBI, Class::DBI, and Data::FormValidator.