Idea: have a modular repo that allows users to easily start a different set of addons
The core repo with mods that apply for all other repos, content not likely to change often.
@CBA_A3, @fp_ace, @acex, @acre2, @CUP_Terrains_Core
(rename @fp_ace to @ace and use default install - disable glasses and earplugs as setting)
Any non-dependency mod (outside of the mentioned above) that makes sense to have for the OTHER repos Examples: fpa_X in @fp, fpz. Stuff like ADR-97, NIArsenal doesn't fit here.
The default repo used for sunday ops unless said otherwise
@CUP Units, Vehicles, Maps (skip cwa maps?), ACE Compats, @NIArsenal, @adr-97. Maps, keep napf, celle2?
Vietnam (entire unsung?) Cambodia map (w/e name it has now). WW2 / IFA with maps.
Testing mods? Dunno. Mechs. RHS?
@fp_gear, @fp_weapons needs some work to filter out what belongs to blue/yellow.
Update bot to allow uploading missions to a specific repo
!upload blue http://mymission.pbo myMission.napf
Uploads missions to \fparma\configurations\blue\missions
Server can only be restarted w/ different repos by admins
- Create folder in fparma called "configurations"
- Create core, blue, yellow under \configurations
- Each sub-folder has a setting.json, \keys and \missions folder
- All deployments inherits from core
- Run "start-blue.sh" from "fparma" folder
#!/bin/sh (pseudo code)
systemctl stop arma3-server, arma3-hc, armasock;
unlink /arma3/server/keys;
for f in $(ls -d /configurations/core/keys/*); do ln -s $f /arma3/server/keys;
for f in $(ls -d /configurations/blue/keys/*); do ln -s $f /arma3/server/keys;
unlink /arma3/server/missions;
for f in $(ls -d /configurations/core/missions/*); do ln -s $f /arma3/server/missions;
for f in $(ls -d /configurations/blue/missions/*); do ln -s $f /arma3/server/missions;
unlink /arma3/server/repo;
ln -s /repo/blue.public/ /arma3/server/repo;
// copy start scripts to server and hc
systemctl start arma3-server, arma3-hc, armasock;
echo "done";