Re: [Bacula-users] connecting bacularis to an existing bacula setup

2024-04-08 Thread Marcin Haba
Hello Steven, Yes, web servers by default listen on port 80 but it is possible to change. Bacularis uses only one port 9097. I mean that after installing Bacularis with the web server, you can just disable listening on port 80 or change it to any other port number. Best regards, Marcin Haba

Re: [Bacula-users] connecting bacularis to an existing bacula setup

2024-04-08 Thread steven
Hi, It will not run on bare metal as it tries to run on port80, but I have apache containers on port 80 and 443 already which was why I went for a docker container to isolate bacularis that runs on 9097 OK but the wizard lacks connectivity to bacula. regards Steven On 9/04/2024 2:16 pm,

Re: [Bacula-users] connecting bacularis to an existing bacula setup

2024-04-08 Thread Marcin Haba
Hello Steven, Bacularis API and Bacularis Web are one application called just Bacularis. So, as I see you already have it. In the installation wizard there is possible to choose if you want to configure API or Web or both (typical case). After installation you need just to go to:

Re: [Bacula-users] connecting bacularis to an existing bacula setup

2024-04-08 Thread Thing
Google it seems does not like my email server...lets try again, sorry if we get a duplicate. Hi, I dont see a bacualris API to install? root@bacula:~# dpkg -l bacula* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/

Re: [Bacula-users] connecting bacularis to an existing bacula setup

2024-04-08 Thread steven
Hi, I dont see a bacualris API to install? root@bacula:~# dpkg -l bacula* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version

Re: [Bacula-users] connecting bacularis to an existing bacula setup

2024-04-08 Thread Marcin Haba
Hello Steven, Of course, you don't need to uninstall anything. Bacula daemons stay where they are. Don't worry, nothing changes here. In that container image description is a sentence: "It can be used to connect external Bacularis API server(s) in containers or outside them." This "outside

Re: [Bacula-users] connecting bacularis to an existing bacula setup

2024-04-08 Thread steven
hi, Ok I am confused.   The way I read it, - for File Daemons bacularis-api-fd,  - for Storage Daemons bacularis-api-sd,  - for Directors bacularis-api-dir. All have the particular bacula daemon built in?    I dont need a daemon, I already have all the daemons running and have been for 6 odd

Re: [Bacula-users] connecting bacularis to an existing bacula setup

2024-04-08 Thread Marcin Haba
Hello Steven, Thanks for your question and feedback after installing the bacularis-web container. I will try to explain it below. For your question if the Bacularis Web wizard wants a Bacularis API - yes Bacularis Web in this container connects to external Bacularis API. Description and purpose

[Bacula-users] connecting bacularis to an existing bacula setup

2024-04-07 Thread steven
Hi, Seeing the release I thought I would give bacularis a go.    I have the bacularis-web docker container running but I cant see any documentation telling me how to connect it to my existing bacula setup. The wizard wants a baculum API?  but this isnt explained. Is there any set by set