Features:

• Easy to setup system
• Can be setup on any DayZ Server. No extra exe or script needed
• Will download any config file you want from Github on server startup
• Use Github for easy access to all configs and easily go back to an older version with a few clicks
• Designed to work with private Github repositories, so nobody can access your files
• syncs only the files, which were actually changed to make as minimal of an impact on your server startup as possible
• The mod uses an external cloudflare application to get the file list of the repository and it will send the github access token with it. If you have a problem with that and don't trust my application is not doing what it should do, deploy your own cloudflare worker, which will do that for you. The tokens are never saved anywhere and are only used to serve the list of files to the DayZ Server.

Setup:

Step 1: Create a Github account

• If you don't already have a Github account, create one at https://github.com/signup
• If you already have a Github account, you can just use that

  Step 2: Create a repository

• Create a New Repository
• Enter a name for your repository. You can choose any name you like. For example DayZ_Configs
• Change the visibility to private, otherwise the mod will complain about using a public repository and anyone could access your files!
• Click on "Create Repository"

  Step 3: Setting up access for the Mod

• For the mod to be able to access the private repository, you need to create a Personal Access token Here (Your profile Image -> Settings -> Developer Settings -> Personal Access Tokens)
• Click on "Generate new Token". If you have 2FA enabled, you might need to enter your 2FA code
• Enter a token name like DayZ Config Mod
• I would recommend setting the expiration date to No expiration if you don't want to enter a new authentication token every now and then. Otherwise set an expiration date and mark it somewhere in your calendar
• Make sure to set the Repository access to Only select repositories
• Click on the dropdown and select only the single repository you created. Do not select additional repositories. The mod cannot automatically select the repository then!
• Now in the permissions section, click on Add Permissions and search for the Contents Permission and add it. Github will automatically select the required Metadata permission too. If you cannot find the permission, you did not select the correct repository access above
• Leave the access level for the permission at read-only
• Click on Generate Token and confirm the settings and click on Generate Token
• Next copy your access token and save it somewhere secure. You will need to put it in your config later

  Step 4: Installing the Mod

• Download the PBOs of this mod and put them directly into the addons folder of your DayZ Server. This mod must not be uploaded to Steam!
• Restart your server to generate the default config file
• open the profile/LBmaster/Config/RemoteConfigs/config.json file and paste your generated token in the githubToken field.
• I would recommend setting a proper servername in the config. This should be unique for all the servers you run. Make sure the name can be a folder name as this will be a folder in your github repository later

  Step 5: Setting up the Github repository

• I would strongly recommend downloading Github Desktop to manage your repository
• In Github Desktop, sign in with your Github account
• In the top left, click on File -> Clone repository... and then search for your Repository you created
• Choose a location where the repository should be saved on your PC
• Click on Clone

  Step 6: Adding files to your Server

• Adding new files is simple, but you have to follow a few rules:
  • The first folder must be named exactly like the servername you entered in the config.json of the mod.
  • inside this folder you need to create 3 subfolders. profile, mission and saves
  • All config files must be put in one of these 3 subfolders. All other files will be ignored!
• To add a new file, make sure you use the same folder structure and names as the mods on your server use
• Example: a file in the profiles folder at LBmaster/Config/Common/test.json would be in SERVERNAME/profile/LBmaster/Config/Common/test.json where SERVERNAME is the servername from your config for this server
• You could also put your types.xml in there at SERVERNAME/mission/db/types.xml

  Step 7: Uploading the changed files

• If you added a new file or changed a file, it needs to be "pushed" to Github
• Open Github Desktop and select your repository and make sure you are in the Changes tab
• Here you see a list of files with their file path and either a green + for new files, and orange dot for changed files or a red - for removed files
• Select all files you want to update. Most of the times you just want to update all files at once
• Write a "commit message" / summary to note down what you changed
• Click on Commit x files to main
• You might be prompted if you want to publish the main branch which is normal for a new repository
• At the top bar you should either see publish branch or the current upload status.
• If someone else did changes to the repository, you first need to download their changes by "pulling" them
• On the next server restart you now should see messages indicating your files were downloaded. Check the scriptlog of your server for the information and possible errors