# emonSD issues created using new scripts + emonhub environment file **URL:** \ **Category:** emonSD\ **Created:** [11 May 2019 09:45 UTC](https://community.openenergymonitor.org/t/emonsd-issues-created-using-new-scripts-emonhub-environment-file/10918 "2019-05-11T09:45:32Z")\ **Posts on this page:** 1\ **Showing post:** 110
**Author:** ![TrystanLea](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/trystanlea/32/31_2.png) [@TrystanLea](https://community.openenergymonitor.org/u/TrystanLea)\ **Post date:** [4 June 2019 16:47 UTC](https://community.openenergymonitor.org/t/emonsd-issues-created-using-new-scripts-emonhub-environment-file/10918/110 "2019-06-04T16:47:34Z")
Following from [emonSD next steps: filesystem & logrotate - #192 by TrystanLea](https://community.openenergymonitor.org/t/emonsd-next-steps-filesystem-logrotate/10693/192) The merge of the emonhub.env version of emonhub is ready to go, the update procedure to install the emonhub.env file is now live in the latest emonpi repository: [add emonhub.env settings file and install as part of update · openenergymonitor/emonpi@693ebd7 · GitHub](https://github.com/openenergymonitor/emonpi/commit/693ebd7d48dff90077f38612f81c14ec1b2c994d) The final step is to merge the following emonhub pull request [Use emonhub.env to set emonhub path names by TrystanLea · Pull Request #82 · openenergymonitor/emonhub · GitHub](https://github.com/openenergymonitor/emonhub/pull/82/files). I will merge this tomorrow unless there are any final objections --- _[View the full topic](https://community.openenergymonitor.org/t/emonsd-issues-created-using-new-scripts-emonhub-environment-file/10918)._