I hadn’t imagined that to be an area where change would be concidered, but for the record I personally do not usually install to /var/www anyway. I prefer to install to /srv/emoncms and symlink to one or more “sites” in the /var/www path, this is the reason I would prefer to see the settings outside the emoncms folder.
Sub-foldering the web-content would make is easier to install to another location eg /srv and just symlink the web-content folder, much like the emailreport and postprocess modules are already, perhaps we can move to a standard name for the web-content folder.
I had already suggested installing the emoncms modules that need to be outside the /var/www path, to a single folder eg “emoncms-modules” so that they were easier to manage and to update. By simply installing all emoncms repos to /srv/emoncms (eg /srv/emoncms/emoncms, /srv/emoncms/app /srv/emoncms/dasboard etc) this would make the auto updater I’m working on even simpler, as it can just loop all folders in /srv/emoncms.
Please see Break out the version to a separate file. by pb66 · Pull Request #745 · emoncms/emoncms · GitHub for more on this.
If you are referring to the source files, yes, or at least initially, once we have a reliable installation and update method, and established locations, we could perhaps review that, but initially nirroring the github repos gives us a small level of consistency to build from.
The data and the settings are not source code and they should not reside in the /srv location. as discussed above, they should reside in the FHS locations unless symlinked to /data for RO sdcards or backing up etc.