You have two options here: a) modify the Pi-Star code so the necessary files are included in the backups, b) install an SSH or FTP of your choice to access Pi-Star's underlying file structure.
---
First, you can modify the backup process as follows:
Code: Select all
rpi-rw
cd /var/www/dashboard/admin
if [ ! "$(grep 'dmr2nxdn' config_backup.php)" ]; then
sudo sed -i 's/dmrgateway $backupDir 2>\&1");/dmrgateway $backupDir 2>\&1");\
\t $output \.= shell_exec("sudo cp \/etc\/dmr2nxdn $backupDir 2>\&1");\
\t $output \.= shell_exec("sudo cp \/etc\/dmr2ysf $backupDir 2>\&1");/g' config_backup.php
fi
Note that this is a temporary fix insomuch as it will get unwound IF any Pi-Star updates are applied to the dashboard code portion of the system. (Unlikely at the moment, since there haven't been much if any fixes applied for a while now - maybe, some day, this fix can get applied so everyone can benefit. And, yes, this code has been tested as I have applied it numerous times on several of my own systems!

)
---
Secondly, you can search out an appropriate Windows- or Linux-based SSH or FTP client and set them up to access your Pi-Star system and the specific directories and files needed for any given situation.
For SSH, I would recommend MobaXterm or Termius, although there are several others that are also adequate; I'm partial to Termius and do most of my command line work via that app, but not usually (bulk) file transfers.
For regular file transfers, especially across multiple systems, especially for binary/zip files, I prefer FTP: the best, IMHO, is a program called WinSCP (euphemistically called "Win Scuppy"). Try it! I think you'll like it!!
Either way, SSH or FTP, watch out for the RO/RW status of your Pi-Star system; also permissions can be a pain sometimes.