Re: Hosting Perl projects

If your going to assemble your projects onto one computer, why not one of your existing ones? I'd have one version control repository (cvs, subversion or to taste) per tarball and use tags to record the history of parts explosions including source versions that went into every release. That way I can write Perl scripts against my repository that can help me quickly track down a culprit change even if for example a bug is reported two releases down the road from its cause.

-M

Free your mind

Comment on Re: Hosting Perl projects

Replies are listed 'Best First'.
Re^2: Hosting Perl projects by dmitri (Priest) on Mar 26, 2007 at 16:01 UTC
Funny as it sounds, I don't really have a permanent development machine... My main computer at home is a Windows box (a Compaq, of all things) running a browser and MS Office for family use. My other boxes come and go... I don't trust myself to do backups anyway, so it'd be better to host somewhere else.	[reply]
Re^3: Hosting Perl projects by Moron (Curate) on Mar 26, 2007 at 16:11 UTC
What I did when in a similar situation a few years ago was repartition and convert my home machine into a dual-booting Linux and XP system - one for work and the other for games (everything else is better on Linux anyway, including OpenOffice.org). Using GRUB you can make the Windows the default boot environment for your family with a few seconds delay to give you time to elect to boot Linux for your work. -M Free your mind	[reply]
Re^3: Hosting Perl projects by hesco (Deacon) on Mar 27, 2007 at 22:15 UTC
I don't trust myself to remember to do backups either. That's why I use a cron job for that purpose. I have cron driven backups going of databases on sql servers and of key directory trees, including the cvs repository I administer for a Coding Network I participate with. Now that a friend has turned me on to the wonders of rsync, I'm consideraing adding an automated rsync (enabled by shared keys between the hosts) to handle the offsite part of the backup project. It was that same friend who, a few years before when I was crying about lost data, mentioned to me, "That data must not have been very important if it wasn't important enough to backup". The truth of that statement certainly didn't make it any easier to hear at the time. But I was still rebuilding my system on a new drive, when I found mysql_backup.cgi in a google search. And as soon as the system was back up, I added that and some tar czf invocations to my crontab. Now configuring such automated backups is an early priority for me whenever I put real work into a new server. -- Hugh if( $lal && $lol ) { $life++; }	[reply]