OK, I've attached the config files I've created for SU (had to zip them to attach). They're plain text so you can inspect them to see how they're setup. I'll explain them in detail below but to use them, they simply need to be uploaded to the server in a sub-folder off the root named six and then they can be used by clicking on links to
sixupdater://ciahome.net/six/cia1.yml
sixupdater://ciahome.net/six/cia2.yml
If it's not already, the mime types file needs to be edited to activate .yml / .yaml as well. I was testing with a nginx server which uses a mime.types file and I had to add
  application/yaml           yml yaml;
but Apache uses the .htaccess file I think
http://httpd.apache.org/docs/2.2/howto/htaccess.html
We can edit CiA1.yml and CiA2.yml any time we want to change what mods we use and SU will automatically check these files and change the presets to match if necessary, meaning users should never need to check the forum and manually install mods again, so hopefully users not having the right mods should become a thing of the past
So if someone could upload the files to the server and edit the mime types file if necessary, we can do a closed-test to check they're working properly (I've only tested on a localhost server so far) and iron out any problems before publishing the links on the homepage.
Now for the details:
The config.yml is the base file and defines the path to the other files under hosts. As you can see, I've set it to
http://ciahome.net/six , so the files need to be stored on the server in a sub-folder named six but I think you can put them anywhere as long as you edit that path.
Then under servers it defines how many servers there are (I've defined one for Tues/Sun and one for Friday) and finally under apps I've setup the TS3 details, which enables the user to launch TS3 and auto-connect from SU.
Then CiA1.yml (for Tues/Sun) defines the name that will appear for the preset in SU and the Required mods. The Allowed mods section is a bit pointless as we don't restrict what mods can be used but I stuck the mods we recommend in there anyway (I put st_hud, mk4 and blakes_pradar in Required mods as I figured they're pretty essential). Obviously SU uses particular names for the mods, so for example if you already had Thirsk in a folder named @Island_Thirsk then SU wouldn't recognise that and would download the mod again to @Thirsk, so you'd want to rename your folder to match the name SU uses to avoid this.
CiA2.yml is for Fridays. You'll note I've set the wrong port in that, to 2712. The reason for this is that SU uses the IP:port to identify servers, so ideally we need to run the server on a different port on Fridays to that used on Tues/Sun. If this isn't possible, we can still use SU but the two presets will both end up showing with the same name like "CiA (Comrades in Arms) ACE" so it would be better if we can use a different port on Fridays. Otherwise it'd be best to just edit the names in both files to something generic like "CiA (Comrades in Arms)".
Although they're not specifed in CiA2.yml, when loading the presets into SU you'll notice it lists some additional mods that you might not recognise. This is because some of the mods included in the Lingor and Duala manual downloads are separated on the Six Network and treated as dependencies, so that they only need to be downloaded/stored once and can be shared amongst several mods. If you look at the armaholic page for Lingor
http://www.armaholic.com/page.php?id=10792 you'll see under "included pbos", it lists:
brg_africa
chn_crocodile
csj_snake
ibr_lcivilians
ibr_plants
MBG_Buildings2
which are the ones that are kept separate on SU. With Duala it's:
brg_africa
ibr_dtowns
mbg_gen_afr_buildings
so you can see that Lingor and Duala both share brg_africa.
The only mods we use that don't appear to be on the Six network are @caa1 and @oac_core so users will need to download those manually but I've listed them in the CiA2.yml, so as long as they're installed to folders with those names then they'll be activated by SU when using the preset. I'll ask if they can be added to the Six network though.
You'll notice I've only listed @CBA_CO in both configs but it appears SU automatically switches between that (which is required for post-beta 100697) and the three separate @CBA, @CBA_A2, @CBA_OA (required for pre-beta 100697) depending on whether the user has the beta enabled or not.