Back
Why Bacularis?
13 Dec 2021, 07:21
Main goal of the Bacularis project is to simplify using the Baculum web interface that it could be used not only by Bacula experts but also by people not familiar too much with Bacula.
Making things simple does not mean reducing existing functionalities but providing new way of use. So both Baculum and Bacularis users have the same set of functions available in a different way.
In Bacularis everything is available in one application. During installation user may choose which component he would like to use in this Bacularis instance (API or Web or both). Native support for the Basic authentication means that users no longer need to modify the web server configuration file for enabling/disabling the Basic auth or the OAuth2 authorization because everything what needed is already inside Bacularis.
We also simplified installation and update process. Bacularis can be installed by the Composer, Docker or by binary packages (deb or rpm).
Below you can find a table with pointed differences between Baculum and Bacularis. This list will be updated on a regular basis as new features are added or modified.
