Difference between revisions of "ERPXE 2.0/Plugin Architecture"
From ERPXE Wiki
| (2 intermediate revisions by the same user not shown) | |||
| Line 15: | Line 15: | ||
==Append== | ==Append== | ||
| − | * | + | * %ip% = your ERPXE server IP. |
| − | * | + | * %tftp% = Where ERPXE tftp folder is (/tftpboot folder by default). |
| − | * | + | * %plugins% = plugins folder 'er/plugins' (by default is located inside the %tftp folder). |
| − | * % | + | * %dir% = current plugins folder |
Latest revision as of 22:31, 20 December 2013
This article is for ERPXE 2.0 development. ERPXE 2.0 is not released yet so this information should not be used to understand current version of ERPXE.
In version 2.x of ERPXE plugins are folder. by default located at /tftpboot/er/plugins.
ERPXE admin searching for folders inside that directory.
The following files are expected (or not) to be inside the plugin directory:
- .ignore - will cause erpxe to ignore the plugin.
- .disabled - will cause the plugin to be disabled.
- .quicklaunch - will cause the plugin to be listed in the quicklaunch menu.
- .locked - will cause the plugin not to be updated ever by erpxe.
- ERPXE will search for .xml files with plugin(s) definition at the root and by default - 2 more levels inside.
Sample of such XML is:
Append
- %ip% = your ERPXE server IP.
- %tftp% = Where ERPXE tftp folder is (/tftpboot folder by default).
- %plugins% = plugins folder 'er/plugins' (by default is located inside the %tftp folder).
- %dir% = current plugins folder
