Subj : Re: multiple nodelist hatches
To   : MeaTLoTioN
From : Vk3jed
Date : Mon Mar 16 2020 15:18:00

-=> On 03-16-20 00:16, MeaTLoTioN wrote to All <=-

 Me> Hey guys,

 Me> Apologies if you get multiple nodelist hatches just now, I just set up
 Me> some automation that will upload and hatch a nodelist every week, using
 Me> git and cron with some bash foo.

 Me> Now I can edit my nodelist stuff and then every Friday at 13:37 UTC it
 Me> will pull the latest version from the remote repo down, compile it,
 Me> upload it to the uk hub, and hatch it all on it's own... assuming it
 Me> doesn't run into any errors.

 Me> This could be pretty useful.

I have a similar system running here.  The nodelist data lives on my Windows
mavhine, where I edit it, and the processing is done by my BBS machine, which
builds the nodelist for distribution and then hatches it out every Friday
morning my time. :)

I am now processing the nodelist for the 3 FTN nets that I host or gate to FTN
- VKRadio, DeveloperNet and MusicalNet.  I am the FTN gate for the latter two,
the host of those nets runs QWK only, so as a result, I need to manage those
nodelists as well.

My system uses MakeNL and a lot of bash foo to process the nodelists, then more
bash foo to prepare TIC files and place them and the nodelists into Mystic's
inbound for hatching to the various nets.

Additional scripting (Perl and bash) are used to update the DNS nodelist for
VKRadio, manage the mounting and unmounting of the Windows share that has the
MakeNL master files and upload a copy of the VKRadio infopack to an external
web server as a backup copy.  These are separate, because they have to run as a
different user and/or on another machine altogether.


.... Does the name Pavlov ring a bell?
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
 * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (1337:2/103)

.