On Tue, 23 Jul 2024 at 09:47, Kees Bakker <ke...@ghs.com> wrote: > Hi Marcin, > > > Thanks for your feedback about trying to use Bacularis docker images. > > Each of these docker image types has in the description a chapter named > "About this image". There is information about what it contains and for > what purposes it could be used. For this "bacularis-web" we can see the > information: > > "It contains a pure the Bacularis web interface without API layer. It can > be used to connect external Bacularis API server(s) in containers or > outside them. If you would like to connect Bacularis API ran in containers, > you can use dedicated for this purpose images: > - for File Daemons bacularis-api-fd > - for Storage Daemons bacularis-api-sd > - for Directors bacularis-api-dir" > > > I didn't want to use those because I already have a working DIR+SD and > FDs. I just want the API, ha ha. >
Hello Kees, Yes, if you want to use this image, having the API(s) is necessary. It is the purpose of this 'bacularis-web' container image - to have a web interface in the container and connect the API instances. The communication between the web interface and API goes through http(s), so for the web interface it does not matter if the API instance is local, remote, in a container or somewhere else. > From the before-you-start: > > "... If you would like to use Bacularis instance in container with Bacula > components located outside the container, you need to prepare it yourself. > Exception of that is the bacularis-web container image that provides a pure > web interface without any API part and it can be connected to any Bacularis > API instance available in the network. See chapter: Install using Docker." > > I believe that this is not going to work with my existing Bacula daemons. > So my conclusion is that I must forget the dockers. > For your Bacula environment, I would propose to start simple and install one Bacularis on this DIR+SD host. This setup provides 90% of the Bacularis functions including DIR and SD configuration. Having Bacularis API on the FDs is useful only for two purposes: - to be able to change the Bacula FD configuration on the web interface - to be able to start/stop/restart the FD component If you don't want any of the listed functions, installation of Bacularis on FD hosts is optional. Even without an API installed there, these FDs will be possible to use on the web interface for backup, restore, statistics, graphs, running jobs...etc. > I have also setup a test system with Bacula DIR+SD and Bacularis Apache. > As far as understand its workings, the API is implemented in PHP, it wants > access to the Postgres database, it wants to run bconsole, it wants to be > able to read/write the configuration files. (The latter is optional and it > is definitely something I don't want.) > Yes, the API is configurable. It enables to provide through the API only these capabilities that are needed (bconsole, catalog, config, actions...etc.). You can read about it here: https://bacularis.app/doc/remote/basic.html#api-capabilities > Before I go that route (installing Apache) I need to spend more time > trying to understand how this works. > Sure. Good luck. Best regards, Marcin Haba (gani) -- "Greater love hath no man than this, that a man lay down his life for his friends." Jesus Christ "Większej miłości nikt nie ma nad tę, jak gdy kto życie swoje kładzie za przyjaciół swoich." Jezus Chrystus
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
