Interface possibilities
-
I'm very new to using TRIGGERcmd so I'm wondering some things.
1: I know you can specify paths in your commands.json file but is there a best place to actually place all your scripts? Obviously you don't want them all over the computer but a specific folder which makes for an easy backup. Should this folder be in the .TRIGGERcmd folder? Would that make for faster triggering?
2: As for back ups these should be done as soon as you've added a new working command to your command.json file. Can TRIGGERcmd not do this?
3: Restoring, can TRIGGERcmd also not do this?TRIGGERcmd can read the command.json file so backing up should be able to do a simple download to the connected device.
Restoring may be a bit more tricky to do from the interface. Script files might also be able to be backed up. Certainly if they were all located in the same universal folder it would make that easier. -
@tuicemen, it's really up to you where you put your scripts. I have a folder on my PC where I generally put mine, just for organization. It doesn't speed up the commands. I don't put them in the .TRIGGERcmdData folder. It would work fine but just doesn't seem to me like the right spot.
For backups I've recommended people create a script that copies your commands.json and/or script files to a folder in Dropbox. You could schedule it or trigger it on-demand.
FYI, the agent does backup your commands.json file to commands.json.backup every time you change it, and it auto-restores the backup if you make a mistake in json formatting.
-
@russ said in Interface possibilities:
FYI, the agent does backup your commands.json file to commands.json.backup every time you change it, and it auto-restores the backup if you make a mistake in json formatting.
Awesome, I did see the commands.json.backup file but didn't realize it auto restored.
I don't like to use the cloud for backups, however I do for some things as well as a back up on disks.
