For some personal sites, what I do is I actually have the fossil repo opened in the web directory. It's .htaccess'd off so that you can't get at it, even if you know it's there.
Then, I've got a cronjob that once every 15 minutes does a 'fossil update release'. Where 'release' is just a tag that I apply to checkins that I feel are ready. I could probably also have a 'vX.Y.Z' tag so that I could force it backwards too, but, they're just personal sites. :) I could probably also wrap it in a script that did more complicated release logic, if I wanted. Just an alternate solution to your problem. Not suggesting that what you want is wrong or invalid. -B On Fri, Feb 4, 2011 at 1:29 PM, Ondrej Nemecek <[email protected]> wrote: > > It's good idea, bud I'd like to deploy any version of source tree > independently of commit. > Of cource - I must know the version on the server and I must deal with > deleted files etc. > > > Dne 4.2.2011 21:57, Clark Christensen napsal(a): >> I do this myself. >> >> I wrote a Perl program to take the output from "fossil status", and deploy >> the >> files via copy (devtest Samba share as target) or FTP (production). It's >> pretty >> straightforward. I have an alias for it, so I just issue "fsl-deploy dev" or >> "fsl-deploy prod". Just have to remember to deploy before the commit. >> >> For the Unix target (prod), it knows to issue a chmod to set *.cgi as >> executable. >> >> -Clark > > > -- > Ondrej Nemecek > icq: 250163477 > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
