The following sections list the changes in reva 0.1.0 relevant to reva users. The changes are ordered by importance.
Reva was not building releases of commits to the master branch. Thanks to @zazola.
Commit-based released are generated every time a PR is merged into master. These releases are available at: https://reva-releases.web.cern.ch
https://github.com/cs3org/reva/pull/402
Reva provided the option to be run with a single configuration file by using the -c config flag.
This PR adds the flag -dev-dir than can point to a directory containing multiple config files. The reva daemon will launch a new process per configuration file.
Kudos to @refs.
https://github.com/cs3org/reva/pull/416
Because @dependabot cannot update in a clean way the vendor dependencies Reva removed support for vendored dependencies inside the project.
Dependencies will continue to be versioned but they will be downloaded when compiling the artefacts.
https://github.com/cs3org/reva/pull/468 https://github.com/cs3org/reva/pull/524
Reva configuration was difficult as many of the configuration parameters were not providing sane defaults. This PR and the related listed below simplify the configuration.
https://github.com/cs3org/reva/pull/545 https://github.com/cs3org/reva/pull/536 https://github.com/cs3org/reva/pull/568
Documentation has been improved and can be consulted here: https://reva.link
https://github.com/cs3org/reva/pull/561 https://github.com/cs3org/reva/pull/545 https://github.com/cs3org/reva/pull/568
Reva did not have any functionality to handle home storages. These PRs make that happen.
https://github.com/cs3org/reva/pull/562 https://github.com/cs3org/reva/pull/510 https://github.com/cs3org/reva/pull/493 https://github.com/cs3org/reva/pull/476 https://github.com/cs3org/reva/pull/469 https://github.com/cs3org/reva/pull/436 https://github.com/cs3org/reva/pull/571