I have several projects on the go all at different stages and I have then on different hdd partitions and regularly swap between them or reinstall for one reason or another. What I would like to do is reuse an EmonCMS API key across multiple installs, only one will ever be live at any given time.
Currently every time I do a fresh install or switch from one image to another I have to edit the oem_gateway.conf file on my forwarding pi. not a difficult job but if I could reuse the same key it would be great to not have to keep changing it.
Also are ALL emonCMS data files in one location, is there one location that if I mount a "data" partition to I can use the same database across several images?
Can local EmonCMS v8 API key be edited ?
Submitted by pb66 on Thu, 27/03/2014 - 01:38I have several projects on the go all at different stages and I have then on different hdd partitions and regularly swap between them or reinstall for one reason or another. What I would like to do is reuse an EmonCMS API key across multiple installs, only one will ever be live at any given time.
Currently every time I do a fresh install or switch from one image to another I have to edit the oem_gateway.conf file on my forwarding pi. not a difficult job but if I could reuse the same key it would be great to not have to keep changing it.
Also are ALL emonCMS data files in one location, is there one location that if I mount a "data" partition to I can use the same database across several images?
Paul