forum.pistar.uk

If you need SSL, you can edit the respective nginx settings within OS itself, put there your certificates etc.
Unless you don't log in to the admin panel from outside, I think it's quite ok to expose the dashboard with port forwarding.

Hi! 1. Generate an API key in BrandMeister: https://brandmeister.network/?page=profile-api 2. Put that key in your Pi-Star configuration at /admin/expert/fulledit_bmapikey.php 3. Then in the /admin page you'll get some managing options like https://1.bp.blogspot.com/-8fkIof5r49k/WrJdxCaZCDI/AAAAAAAB...

In case of SMS or any other readable data — is it possible to implement displaying its contents in the dashboard?

Thanks.

Thank you very much!

The issue started with this commit:
When the binaries are reverted to a previous version, everything works again.

Hi!

After the latest Pi-Star upgrade, there's no sending of callsign/ID to the station. Nothing appears, like in analog mode.

Pure YSF reflectors work fine.

Tested on my Yaesu FT-70D.

Why do you need the GUI frontend? Use a shell script instead, like this one: #!/bin/bash backupDir="/tmp/Pi-Star_Config_${HOSTNAME}_`date +%d-%b-%Y`" backupZip="${backupDir}.zip" mkdir -p ${backupDir} cp -r \ /etc/wpa_supplicant/wpa_supplicant.conf \ /etc/ircddbgateway \ /etc/mmd...

The update of /usr/local/etc/YSFHosts.txt can be commented out in /usr/local/sbin/HostFilesUpdate.sh , just add a # before this line: curl --fail -o ${YSFHOSTS} -s http://www.pistar.uk/downloads/YSF_Hosts.txt Or just make the file immutable by: chattr +i /usr/local/etc/YSFHosts.txt After that even r...

By default, when trying to make a private call to 1234567 you may end up in the TG 34567 . It happens because the respective contacts should first be added to the /usr/local/etc/TGList_BM.txt file in ID;2;CALLSIGN;DESCRIPTION format. TGList_BM.png To add all calls from your country (Latvia in this e...