On 22-07-2024 17:51, Marcin Haba wrote:
On Mon, 22 Jul 2024 at 17:31, Kees Bakker via Bacula-users
<bacula-users@lists.sourceforge.net> wrote:
Hi,
The docker bacularis-web [1] asks me to add a Baculum [2] API
instance.
What exactly is that?
I already have a functioning Bacula system with a Dir/SD and several
FDs. I am looking
for a replacement of the good old BAT and was hoping that Bacularis
would be it.
[1] https://hub.docker.com/r/bacularis/bacularis-web
[2] Could this be a left over after renaming Baculum -> Bacularis?
Hello Kees,
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.
For the question about what is the API, to understand the concept, I
would propose to read these two chapters in the Bacularis documentation:
1. Component relationship and characteristic:
https://bacularis.app/doc/brief/introduction.html#component-relationship
2. Before you start:
https://bacularis.app/doc/brief/before-you-start.html
They can answer your questions. If not, please let us know. Thanks in
advance.
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.
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.)
Before I go that route (installing Apache) I need to spend more time
trying to understand how this works.
For the question about Baculum API, yes, it is a left over :-) Thanks
for catching it. We will fix it quickly.
Good luck.
Best regards,
Marcin Haba (gani)
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
