in reply to Module-starter, using modules, and testing

I recommend to use local::lib and install your modules to a local directory. local::lib makes that painless, for me it just worked (but I really had to read the documentation :-)

For things like testing all modules, you could write a generic script that visits each project folder, and then runs a particular command there - either make test or make install or prove -Ilib -r t/ or whatever.

It shouldn't really matter if you do that on a "local" or a "remote" host, the task stays the same. Synchronization should happen via a source control system, on the "remote" host you can just do a $your_scm update/pull/fetch/whatever in each project folder.

Perl 6 - links to (nearly) everything that is Perl 6.