Difference between revisions of "Changelog Regiboxd"

From regify WIKI
Jump to navigation Jump to search
Line 8: Line 8:
  
 
* '''Changed API functions'''
 
* '''Changed API functions'''
 +
** All given path values provided by JSON have to be absolute pathes (including drive letter on Windows).
 
** '''getBoxInfo''' now returns<pre>"ownerEmail" : "example@regify.com", "localOn" : true</pre>instead of the initial<pre>"state": 16</pre>''localOn'' represents ''state: 16'' and ''ownerEmail'' was added.
 
** '''getBoxInfo''' now returns<pre>"ownerEmail" : "example@regify.com", "localOn" : true</pre>instead of the initial<pre>"state": 16</pre>''localOn'' represents ''state: 16'' and ''ownerEmail'' was added.
 
** '''newConfig''' supports new additional values: ''keepRemovedBoxes'', ''eventsToSyslog'' and ''eventLogPath''.
 
** '''newConfig''' supports new additional values: ''keepRemovedBoxes'', ''eventsToSyslog'' and ''eventLogPath''.

Revision as of 15:00, 18 September 2020

Announcement of new regiboxd V2

The backend of regiboxd was completely renewed and updated. Therefore, there were some new features added. Also, a few API functions slightly changed. You will have to adapt your code if you use the changed functions!

  • Changed folders
    • The request folder changed from "drops" to "req".
      Example changed from C:\example\boxconfig\drops\request to C:\example\boxconfig\req\request.
    • The response folder changed from "tmp" to "res".
      Example changed from C:\example\boxconfig\tmp\response to C:\example\boxconfig\res\response.
  • Changed API functions
    • All given path values provided by JSON have to be absolute pathes (including drive letter on Windows).
    • getBoxInfo now returns
      "ownerEmail" : "example@regify.com", "localOn" : true
      instead of the initial
      "state": 16
      localOn represents state: 16 and ownerEmail was added.
    • newConfig supports new additional values: keepRemovedBoxes, eventsToSyslog and eventLogPath.
    • getBoxList response was changed to return a standard status object instead of just the array. Now it also includes metrics.
    • invite, the roleId value 2 (read/write/publish) has been removed. Existing data will be migrated. Please note that "publishing" is no longer a regibox internal feature. It has to become implemented separately (like in regibox Manager).
    • unfollowBox has been removed and rolled into deleteBox. deleteBox will automatically unfollow if the box is not owned and else delete it.
    • Please refer to included PDF documentation for more detailed explanation of the parameters and functions.
  • New API functions
    • acceptInvite
    • getActivities
    • getConfig
    • getFileList
    • getPastVersion
    • getRecoveryList
    • getResource
    • getUserList
    • getVersionList
    • recoverVersion
    • resetConfig
    • restoreFile
    • setConfig
    • setUser
    • Please refer to included PDF documentation for more detailed explanation of the new functions.

Please also note that the new regiboxd setup for Windows is now creating a start menu shortcut for the PDF documentation.

2019-05-09 / regiboxd V1.6.2 (public release)

Patch release

  • Internal: Handle websocket connections that are gone without any notification (eg TCP/IP lines drop silently by defect firewall).

2019-02-20 / regiboxd V1.6.1 (public release)

Patch release

  • API: Removed any usage of zuid and hexUid from the API. Now there is only uid.
  • New: Adding configuration information to diagnostics for better analysis.
  • New: Adding performance statistics to diagnostics for better analysis.
  • Fix: Include documentation in debian package.
  • Fix: Add missing chinese templates.
  • Fix: Fixed diagnostics missing cURL entries if not started from the beginning by using -v switch.
  • Internal: Improve behavior under high load introduced by missing websockets.
  • Internal: Enhance websocket usage to fit size constrained environments.

2018-10-04 / regiboxd V1.6.0 (public release)

First regiboxd release (regibox SDK)

  • Allows installation of regibox as daemon/service (Linux and Windows, 64 Bit).
  • Allows management of multiple instances with independent configurations.
  • Control regiboxd instances using command-line options in flexible JSON syntax.
  • Find the documentation in the installation folder (Windows) or /usr/share/regiboxd/ (Linux).