| Newsgroups |
gmane.network.everybuddy.user |
| Message-ID |
<[email protected]> |
If you just want to mirror the nightlies, you could just:
wget http://archives.wincoll.ac.uk/~c/eb-lite/nightlies/eb-lite-TIME.tgz
..where TIME is YYYYMMDD. This is easily doable with a shell script
running on a cron job - look up the "format string" capabilities of the
"date" command. I'd give you the commands I use in the shell script that
makes those nightly tarballs, but the machine's down and I can't remember
the syntax off the top of my head :-\
Meredydd
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> [email protected] wrote:
> > Thanks, that would be brilliant. How would you prefer to set it up? I'm
> > afraid rsync *to* that machine isn't really an option, but if you want
I
> > could set up a cron job to sync the website onto your machine (making
the
> > connection *from* archives.wincoll.ac.uk).
>
> I just tried using wget manually (wget -m) and unfortuately it doesn't
> work that well with dynamic driven sites. The downloads however could
> be done this way. Mind you, using something secure like sftp isn't
> impossible. (I'd rather not use plain FTP, but that's there too).
>
> > Alternatively, we could make periodic manual copies of the site
> itself, and
> > you could just auto-mirror the nightly builds (produced at 4am each
> > morning, with a consisent naming scheme).
>
> I presume this is 4AM GMT? That shouldn't be a problem, I'll tell the
> machine to do it at 6:00PM (GMT+10), the easiest bet is to use wget to
> mirror the page in question and download the linked files. Perl may be
> a more effecient way of doing this as it allows for intelligent
> mirroring, as all we really want to mirror is the nightly tarballs.
>
> For this, is there an actual page I need to point the perl script (or
> wget) at?
>
> The thing I need to watch here is how much this eats into our download
> budget. We're allowed a 3GB limit per month, unfortunately. Broadband
> here in Australia is extremely expensive compared with other countries.
>
> If you want, you could also set up SFTP (or plain FTP) with access to
> the HTTP accessible areas on the machine. If our server is the only
> likely user, you could also set up the firewall to only allow
> connections from 202.47.55.78, therefore making it effectively closed to
> the rest of the internet.
>
> Anyway, those are just some ideas.
> - --
> +-------------------------------------------------------------+
> | Stuart Longland stuartl at longlandclan.hopto.org |
> | Brisbane Mesh Node: 719 http://stuartl.cjb.net/ |
> | I haven't lost my mind - it's backed up on a tape somewhere |
> | Griffith Student No: Course: Bachelor/IT @ Nathan |
> +-------------------------------------------------------------+
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1-nr1 (Windows 2000)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQE+j+fMIGJk7gLSDPcRAp1+AKCL1tHIbKS4ipGLAiG2kzRS8KPKIACeImv0
> 4cWLrcxw1iBI5A6XVSxKRt4=
> =PZIJ
> -----END PGP SIGNATURE-----
>
>
---------------------------------------------
This message was sent using Endymion MailMan.
http://www.endymion.com/products/mailman/