In light of the recent discussion on emonSD logs, earlier discussions on the emonSD update process, the variety of solutions and whether we should support a more generic install/build process this thread is a starting point for thinking about the next step. The next image is also in our development…

[image] TrystanLea: I still need to look the idea of supporting multiple emoncms installations on one machine I suspect that will simply be a need to configure the initial path layout so it is extensible. Perhaps just offer a commented out alternative structure for a multi install environmen…

[image] borpin: I suspect that will simply be a need to configure the initial path layout so it is extensible I think that may well be the case, should be straightforward.

A little more progress on this. There is now a wifiAP install script, with the access point tested and working. Default paths changed and configurable to: /opt/emon and emoncms data: /var/opt/emon/phpfina… changes to emonPiLCD script that make it path flexible merged into master I’ve run the buil…

Noting your comment here @borpin for inclusion Unexpected output from git describe - #11 by borpin

Further progress on the install script: Merged multienv branch of backup module into master branch to support flexible install path, update install script to pull in master branch. Multi environment support for backup module by TrystanLea · Pull Request #23 · emoncms/backup · GitHub Sync module …

:anguished: It’s annoying that after you split the topic, I no longer get notification emails to tell me there’s been any activity. Short of changing discourse to also split the notifications, can I suggest that as a courtesy whenever anybody splits a topic, they post a message to the original topic…

[image] TrystanLea: The installation on a stock raspbian stretch image can be started with: [image] emonSD next steps: filesystem & logrotate My draft readme for the install process is available in the folder here: I’m not sure if you are using the latest Raspbian Lite image, but the re…

@TrystanLea , one other point as part of the install, I think this needs a 'default.config.ini` file that can be copied and changed for use but ignored by git. At the very least a warning to the user that it is using the default config ‘do you want to continue’ type question.

[image] borpin: I suspect the file system has already been expanded. Raspbian images now resize automatically, If you look at a virgin cmdline.txt there is a entry like init=/some/path/init_resize.sh, if you delete that before putting into a Pi, it will not resize. I think it completes the fu…

[image] pb66: Raspbian images now resize automatically For the install script I think we should work on the basis it has been resized so need to shrink first. Goes back to where we started - do we actually need to do so?

Community

OpenEnergyMonitor

Home
Docs
Community
Shop
Search

OpenEnergyMonitor Community

emonSD next steps

emonSD

show post in topic

Home
Categories
Guidelines
Terms of Service

Powered by Discourse, best viewed with JavaScript enabled