# Emoncms 9.8.3 released to emonPi Stable branch

**URL:** <https://community.openenergymonitor.org/t/emoncms-9-8-3-released-to-emonpi-stable-branch/3759>\
**Category:** emonPi\
**Created:** [18 April 2017 14:28 UTC](https://community.openenergymonitor.org/t/emoncms-9-8-3-released-to-emonpi-stable-branch/3759 "2017-04-18T14:28:42Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![glyn.hudson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/glyn.hudson/32/35003_2.png) [@glyn.hudson](https://community.openenergymonitor.org/u/glyn.hudson)\
**Post date:** [18 April 2017 14:28 UTC](https://community.openenergymonitor.org/t/emoncms-9-8-3-released-to-emonpi-stable-branch/3759/1 "2017-04-18T14:28:42Z")

</div>

Emoncms 9.8.3 has been release to Stable branch:

### See [Emoncms 9.8.3 change log](https://github.com/emoncms/emoncms/releases/tag/9.8.3).

The emonPi will pull from the stable branch during the emonPi / RFM69Pi update process (setup \> Admin \> emonPi update)

9.8.3 requires an update to Emoncms `settings.php`, I’ve [added into the emonPi update script](https://github.com/openenergymonitor/emonpi/pull/50) a md5sum check to see if any user changes are present in `settings.php`; if no user changes are present (compared to `default.emonpi.settings.php`) the update process updates the emonPi’s `settings.php` to latest version.

---

<div class="post-metadata">

**Author:** ![Bill.Thomson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/bill.thomson/32/1834_2.png) [@Bill.Thomson](https://community.openenergymonitor.org/u/Bill.Thomson)\
**Post date:** [18 April 2017 14:47 UTC](https://community.openenergymonitor.org/t/emoncms-9-8-3-released-to-emonpi-stable-branch/3759/2 "2017-04-18T14:47:13Z")

</div>

Glyn,

Would it make more sense to list the change log with the newest version at the top?

The way it is now, the first thing you see is:

## Emoncms 9.8.3 | 2017.04.18

glynhudson released this an hour ago

## 9.8.2 | 2017.03.03

Granted, one only has to look a bit further down their screen to see:

## 9.8.3 | 2017.04.18

But, as more entries are made, the newest release info will get pushed down the list vice being at the top where it’s quickly and easily spotted.

---

<div class="post-metadata">

**Author:** ![glyn.hudson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/glyn.hudson/32/35003_2.png) [@glyn.hudson](https://community.openenergymonitor.org/u/glyn.hudson)\
**Post date:** [18 April 2017 15:39 UTC](https://community.openenergymonitor.org/t/emoncms-9-8-3-released-to-emonpi-stable-branch/3759/3 "2017-04-18T15:39:09Z")

</div>

Sure, good idea. I’ve swapped them round.

The 9.8.2 changes were only included since we skipped doing an official release for 9.8.2. e.g 9.8.1 has its own release entry:

> **[Releases · emoncms/emoncms](https://github.com/emoncms/emoncms/releases)**
>
> Web-app for processing, logging and visualising energy, temperature and other environmental data - emoncms/emoncms

---

<div class="post-metadata">

**Author:** ![borpin](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/borpin/32/193_2.png) [@borpin](https://community.openenergymonitor.org/u/borpin)\
**Post date:** [18 April 2017 18:50 UTC](https://community.openenergymonitor.org/t/emoncms-9-8-3-released-to-emonpi-stable-branch/3759/4 "2017-04-18T18:50:04Z")

</div>

Could the Change Log have a link to the update instructions. I have just had a look on the ‘Guide’ and ‘Resources’ but cannot find the instructions. I do it so rarely that it is always a pain to try and find the update instructions. I think they are buried in GitHub somewhere 🙂

Also, is there any easy way to discover whether any modules need updating?

[edit]  
I remember this [thread](https://community.openenergymonitor.org/t/admin-display-currently-installed-emoncms-modules/1954/21) from last year. Could the code be changed to list the installed version and check for the current version on GitHub so alerting the user an update is available. Even better if there was a button to enable the update for each module.

---

<div class="post-metadata">

**Author:** ![glyn.hudson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/glyn.hudson/32/35003_2.png) [@glyn.hudson](https://community.openenergymonitor.org/u/glyn.hudson)\
**Post date:** [18 April 2017 19:24 UTC](https://community.openenergymonitor.org/t/emoncms-9-8-3-released-to-emonpi-stable-branch/3759/5 "2017-04-18T19:24:16Z")

</div>

On the emonPi the update is an automated on button press. (setup \> Admin \> emonPi update)

I take it you’re running Emoncms on a normal server? The version number is shown on the bottom of the page (once logged in).

Are you running the Master or Stable branch?

Updating is just a case of cd’ing into the Emoncms folder e.g `/var/www/emoncms` and running `$ git pull` and doing the same for each module e.g. `cd /var/www/emoncms/Modules/dashboard`

---

<div class="post-metadata">

**Author:** ![borpin](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/borpin/32/193_2.png) [@borpin](https://community.openenergymonitor.org/u/borpin)\
**Post date:** [18 April 2017 19:58 UTC](https://community.openenergymonitor.org/t/emoncms-9-8-3-released-to-emonpi-stable-branch/3759/6 "2017-04-18T19:58:40Z")

</div>

Yes own install on a Pi

Master or Stable, what ever the original install instructions said 🙂 How can I check? is it in the .git? Stable I am guessing.

Would it not be possible for the admin page to interrogate this file and put the information there? Perhaps a separate version status page would be a good addition? Is is apin to have to go into each module folder to test to see if there is an update or not.

Is there not an upgrading page anywhere? Do I need to stop any of the processes?

There is a comment on the need to update the settings file. Is there any more detail anywhere?

Cheers

---

<div class="post-metadata">

**Author:** ![pb66](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/pb66/32/27_2.png) [@pb66](https://community.openenergymonitor.org/u/pb66)\
**Post date:** [18 April 2017 20:06 UTC](https://community.openenergymonitor.org/t/emoncms-9-8-3-released-to-emonpi-stable-branch/3759/7 "2017-04-18T20:06:06Z")

</div>

@borpin, I use this little bash script saved as `update_emoncms` and made executable.

```auto
#!/bin/sh
# emoncms updater script

EMONCMS_DIR=/var/www/html/emoncms
printf "\nUpdate emoncms....\n"
git -C $EMONCMS_DIR pull
for M in $EMONCMS_DIR/Modules/*
  do
    if [-d "$M/.git"]; then
      printf "\nUpdate emoncms/$(basename $M)....\n"
      git -C $M pull
    fi
  done

```

Then just using the `update_emoncms` command does just that, including all the Modules too.

---

<div class="post-metadata">

**Author:** ![borpin](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/borpin/32/193_2.png) [@borpin](https://community.openenergymonitor.org/u/borpin)\
**Post date:** [18 April 2017 20:23 UTC](https://community.openenergymonitor.org/t/emoncms-9-8-3-released-to-emonpi-stable-branch/3759/8 "2017-04-18T20:23:34Z")

</div>

@pb66 That is exactly what I am after to update the repos. 😀

Does anything need to be stopped and started?

Is there any way (command) to list the local release and the remote release?

---

<div class="post-metadata">

**Author:** ![borpin](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/borpin/32/193_2.png) [@borpin](https://community.openenergymonitor.org/u/borpin)\
**Post date:** [18 April 2017 20:41 UTC](https://community.openenergymonitor.org/t/emoncms-9-8-3-released-to-emonpi-stable-branch/3759/9 "2017-04-18T20:41:32Z")

</div>

So I played a bit more but could not understand why the local command

```
git describe --tags

```

gave me 9.9.0

Then I noticed this…  
 ![](https://community.openenergymonitor.org/uploads/default/original/2X/8/839f0381224db7bc761b55d8cea4c92e769648a7.PNG)

The Tag is 9.9.0 for version 9.8.0 ☹

Subsequent releases are correct! Still do not understand git 😖

---

<div class="post-metadata">

**Author:** ![glyn.hudson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/glyn.hudson/32/35003_2.png) [@glyn.hudson](https://community.openenergymonitor.org/u/glyn.hudson)\
**Post date:** [18 April 2017 23:50 UTC](https://community.openenergymonitor.org/t/emoncms-9-8-3-released-to-emonpi-stable-branch/3759/10 "2017-04-18T23:50:46Z")

</div>

> [@borpin](#):
>
> The Tag is 9.9.0 for version 9.8.0

Sorry, that looks like an error 😖 , all other versions are correctly tagged, onwards and upwards 🙂

To find out which branch your on use:

`$ git branch`

If you just cloned using `git clone` you will be on the default `master` branch. To switch to `stable` (recommended if you don’t want to be involved with dev) use:

`$ git checkout stable`

* * *

> [@pb66](#):
>
> , I use this little bash script saved as update\_emoncms and made executable.

Nice script, do you think it would be a good idea for us to add this to the Emoncms [useful scripts repo](https://github.com/emoncms/usefulscripts) ?

---

<div class="post-metadata">

**Author:** ![pb66](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/pb66/32/27_2.png) [@pb66](https://community.openenergymonitor.org/u/pb66)\
**Post date:** [19 April 2017 08:59 UTC](https://community.openenergymonitor.org/t/emoncms-9-8-3-released-to-emonpi-stable-branch/3759/11 "2017-04-19T08:59:31Z")

</div>

> [@glyn.hudson](#):
>
> Nice script, do you think it would be a good idea for us to add this to the Emoncms useful scripts repo ?

I don’t see why not.

---

<div class="post-metadata">

**Author:** ![pb66](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/pb66/32/27_2.png) [@pb66](https://community.openenergymonitor.org/u/pb66)\
**Post date:** [19 April 2017 09:08 UTC](https://community.openenergymonitor.org/t/emoncms-9-8-3-released-to-emonpi-stable-branch/3759/12 "2017-04-19T09:08:00Z")

</div>

> [@borpin](#):
>
> Does anything need to be stopped and started?

Not in my experience, but I will leave that for others to decide, you will need to check if the database needs updating via the admin page afterwards (perhaps that could be added to the script at somepoint using the api call?) and it is very important to check if the settings.php needs changing/updating etc.

The script can be improved a lot, it was just a quick and dirty way of avoiding having to CD in and out of the different folders and doing pulls in each.

---

<div class="post-metadata">

**Author:** ![glyn.hudson](https://community.openenergymonitor.org/user_avatar/community.openenergymonitor.org/glyn.hudson/32/35003_2.png) [@glyn.hudson](https://community.openenergymonitor.org/u/glyn.hudson)\
**Post date:** [19 April 2017 12:20 UTC](https://community.openenergymonitor.org/t/emoncms-9-8-3-released-to-emonpi-stable-branch/3759/13 "2017-04-19T12:20:41Z")

</div>

> [@pb66](#):
>
> I don’t see why not.

Done 🙂

> <https://github.com/emoncms/usefulscripts/commit/5cb36f68bd59cea4cab87da819130350f20ba4a9>

Thanks