# Ghost one click update button in the admin interface **URL:** \ **Category:** Ideas\ **Created:** [April 26, 2018, 8:04pm UTC](https://forum.ghost.org/t/ghost-one-click-update-button-in-the-admin-interface/1091 "2018-04-26T20:04:43Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![dsecareanu](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/dsecareanu/32/413_2.png) [@dsecareanu](https://forum.ghost.org/u/dsecareanu)\ **Post date:** [April 26, 2018, 8:04pm UTC](https://forum.ghost.org/t/ghost-one-click-update-button-in-the-admin-interface/1091/1 "2018-04-26T20:04:43Z")
I know that the update process is complicated and may run into issues (i.e. file or user permissions), but I think a one click update button in the admin interface would help with running the update. However, this is complicated by the way that Ghost installation process works (requiring a separate user and not really working under a generic, non-shell user, such as nginx or www-data or something similar). Also, there is no clear indication in the admin interface when an update is required (a simple notification of some sort) or what current version you’re running (unless you click on the site name and then on the about Ghost link) and this could be easily fixed with a footer bar or a simple mention of the current Ghost version somewhere in the sidebar (above the view site link, which I would actually place somewhere at the top near the name of the site). I think this is important mainly for security reasons and I’m glad that there is a ticket open for it: > > > Very related, but separate to #1260 > > Regardless of any other functionality rela…ted to updates, the following should exist as a standalone thing: > > Ghost should automatically check what the latest version of Ghost is and compare it to the version which is currently being used. > > If an update is available, we should fire a green notification that reads: > > \> A new version of Ghost is available! Hot damn. \[Upgrade now\](#) > > Upgrade now should go to http://ghost.org/download/ for now. If/when #1362 is merged then it should go to ugly debug tools > > \*\*Update:\*\* > > The endpoint to check for updates also records some anonymous usage statistics. The endpoint requires a POST request to https://updates.ghost.org/ with a JSON-encoded body containing the following keys. blog\_id must be provided in order for saving to occur. > \- blog\_id - string - a hash of the blog URL > \- ghost\_version - string > \- node\_version - string > \- npm\_version - string > \- env - string - production/development > \- database\_type - string - SQLite, MySQL, pg > \- email\_transport - string - mail.options.service, or otherwise mail.transport > \- blog\_created\_at - unix epoch timestamp - created\_at timestamp from settings.dbHash > \- post\_count - integer - total number of posts > \- user\_count - integer - total number of users - always 1 for now > \- theme - string - value of settings.activeTheme > \- apps - text - comma separated list of activePlugins - empty for now > > Opting out of update notifications should be possible with a setting in config.js of \`updateCheck: false\`. > > The end point returns the time which the next check may be performed. Ghost should check to see if the current time is greater than the next update allowed time, and if it is, fire another update. > > The update time returned by the endpoint should be 24 hours after the request was made, but this may change. Our sessions currently last 12 hours, so we should only check once per session. Also, I would consider an auto update option (at least at command level via crontab, for example). Thanks! ---
**Author:** ![Kevin](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kevin/32/32_2.png) [@Kevin](https://forum.ghost.org/u/Kevin)\ **Post date:** [April 27, 2018, 7:58am UTC](https://forum.ghost.org/t/ghost-one-click-update-button-in-the-admin-interface/1091/2 "2018-04-27T07:58:04Z")
> [@dsecareanu](#): > > I think this is important mainly for security reasons If there are any security-related issues then you’ll see an update notification. With the switch to weekly releases the constant upgrade notifications became very annoying which was why we switched to only notifying for major updates or when an upgrade is necessary for security.