In 2.9 we have a compatibility mode where /etc/amportal.conf gets written out. However, that will eventually go away (2.10 maybe, 2.11…)
The module subsystem is not typically able to write to the location where amportal is located (/usr/local/sbin for example) so we need to eventually get that migrated. If an upgrade is done with the install_amp script then this is not an issue as amportal will get updated.
The best solution I have currently (better ideas welcome), is:
- framework module can put a copy of amportal into the AMPBIN directory as part of the module install (will not be there for install_amp installs)
- freepbx_engine, which does run as root, van check for the existence of the amportal script in the local directory and if found, can move it to the AMPSBIN directory replacing the old amportal.
Then next time freepbx_engine is run by the user, their amportal script is updated.