Skip to content

v1.101.0
Compare
Choose a tag to compare
@joeuhren joeuhren released this 10 Jul 01:56
· 100 commits to master since this release
v1.101.0
42a59ab
This commit was signed with the committer’s verified signature.
joeuhren Joe Uhren
GPG key ID: 19066824FBCF96C7
Learn about vigilant mode.

We are proud to announce the release of eIquidus explorer v1.101.0. This is mostly a maintenance release with various improvements and bug-fixes. The update script has been perfected so that manual restarts of the explorer are no longer necessary after updating since the update script now handles restarting automatically.

The only database change for this release was a small change to the networkhistory collection to split difficulty into difficulty_pow and difficulty_pos. However, a number of new settings were added to the settings.json file that you may want to review and configure appropriately.

NOTE: If you have existing NetworkHistory data from before the v1.100.0-57b6dd7 update, it will be automatically assumed to be POW. If it was actualy POS, you will need to either manually fix the data in mongo or simply wait a couple hours while syncing to eventually push the old data out of the chart.

How to Upgrade

  1. If you are running an older version than v1.100.0-bae4d50, you must first shut down the explorer manually before updating to prevent problems [SEE IMPORTANT NOTE BELOW]
  2. Download the updated code changes with the cmd: git pull (or npm run update-explorer if using a more recent version that supports this cmd)
  3. Review the changes to the settings.json.template file and consider adding and configuring the newly added settings. NOTE: An effort has been made to allow previous settings.json files to work using default values for new settings, without actually adding the newest config changes, but you may receive deprecation warning messages when you start the explorer and you may also still need to manually fix image paths and change default settings where applicable.

IMPORTANT NOTE: If you were running an explorer version that is older than v1.100.0-bae4d50 and you did not shut down the explorer before performing a code update, you will be unable to shut down or restart the explorer using the usual built-in cmds due to breaking changes. Therefore, you will need to type out the full stop cmd this one time only, and from now on going forward you should no longer need to even stop the explorer for any update, as it is now built into the update cmd.

If running using pm2 and you cannot stop the explorer, you can stop using the following full cmd syntax:

Windows:

pm2 stop ./bin/instance

Linux and other OS's:

node node_modules/pm2/bin/pm2 stop ./bin/instance

If running using forever and you cannot stop the explorer, you can stop using the following full cmd syntax:

All OS's:

node node_modules/forever/bin/forever stop ./bin/cluster

Notable Changes

Assets 2
Loading