borpin
7 September 2018 19:25
4
I raised a PR on GitHub quite some time ago about the paths in the backup module being hard coded (not even a variable to set in the script) which is a real PITA. IIRC, to use the backup module from EmonCMS you need the feedrunner(?) script but I didn’t understand why at the time.
I knew I’d looked at this before.
And the PR
But no one picked it up.
The backup module is separate from the main core.
I’m not familiar with the Prebuilt image I’m afraid. My issues revolved around the install not being on a pi.
emoncms:master ← borpin:master
opened 10:52PM - 27 Feb 18 UTC
The task is to make the backup module work on non pi systems.
I have modified… this so that the config file now resides in the php folder and is read by both the php side and the bash side. I am not sure if this is a security issue or not.
I have also added in some file exist checks for non EmonPi setups.
Phpfiwa was not backed up.
This now needs more development in identifying different base systems and reacting accordingly.
feedwriter is not stopped currently (commented out) as I don't have it installed. The service could be checked for existing & running.
As I say, just a start on this.
Do you have redis enabled?