# emonSD next steps **URL:** \ **Category:** emonSD\ **Created:** [18 March 2019 15:12 UTC](https://community.openenergymonitor.org/t/emonsd-next-steps/10426 "2019-03-18T15:12:03Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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:** [18 March 2019 15:23 UTC](https://community.openenergymonitor.org/t/emonsd-next-steps/10426/2 "2019-03-18T15:23:13Z")
In the pre-merge emoncms v9.9.6 thread we discussed making the update process compatible with non emonSD systems [Emoncms V9.9.6 Stable merge (pre-merge check) - #33 by TrystanLea](https://community.openenergymonitor.org/t/emoncms-v9-9-6-stable-merge-pre-merge-check/9914/33) I made the emoncmsupdate script less emonSD specific and you asked @borpin for it to be included in the usefulscripts repository. This line of development seems separate from the docker side of things. Do we need a generic image build script as well? e.g for DietPi? Discussing with Glyn, the advantage of docker is that we can specify the versions of all the dependencies and have a common environment. Having a script that can run on multiple distributions might fall foul of this, with issues resulting from different dependency versions etc. What do you think @borpin? --- _[View the full topic](https://community.openenergymonitor.org/t/emonsd-next-steps/10426)._