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 (gani) On Tue, 9 Apr 2024 at 06:29, steven <ste...@graywitch.co.nz> wrote: > 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, Marcin Haba wrote: > > 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: > > http://yourhost:9097 > > Best regards, > Marcin Haba (gani) > > On Tue, 9 Apr 2024 at 01:15, Thing <thing.th...@gmail.com> wrote: > >> 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 >> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) >> ||/ Name Version Architecture Description >> >> +++-========================-==============-============-===================================================================== >> ii bacula-bscan 9.6.7-7 amd64 network backup >> service - bscan tool >> ii bacula-client 9.6.7-7 all network backup >> service - client metapackage >> ii bacula-common 9.6.7-7 amd64 network backup >> service - common support files >> ii bacula-common-mysql 9.6.7-7 amd64 network backup >> service - MySQL common files >> un bacula-common-pgsql <none> <none> (no description >> available) >> un bacula-common-sqlite3 <none> <none> (no description >> available) >> ii bacula-console 9.6.7-7 amd64 network backup >> service - text console >> ii bacula-director 9.6.7-7 amd64 network backup >> service - Director daemon >> un bacula-director-database <none> <none> (no description >> available) >> ii bacula-director-mysql 9.6.7-7 all network backup >> service - MySQL storage for Director >> un bacula-director-pgsql <none> <none> (no description >> available) >> un bacula-director-sqlite3 <none> <none> (no description >> available) >> un bacula-doc <none> <none> (no description >> available) >> ii bacula-fd 9.6.7-7 amd64 network backup >> service - file daemon >> ii bacula-sd 9.6.7-7 amd64 network backup >> service - storage daemon >> un bacula-sd-mysql <none> <none> (no description >> available) >> un bacula-sd-pgsql <none> <none> (no description >> available) >> un bacula-sd-sqlite3 <none> <none> (no description >> available) >> ii bacula-server 9.6.7-7 all network backup >> service - server metapackage >> ii bacularis 2.7.0~bullseye all The Bacularis >> WebGUI enables administration and managing Bacula jobs. >> ii bacularis-apache2 2.7.0~bullseye all This package >> provides the Apache configuration for Bacularis. >> un bacularis-lighttpd <none> <none> (no description >> available) >> un bacularis-nginx <none> <none> (no description >> available) >> root@bacula:~# >> >> >> I am finding the naming convention /description difficult to understand. >> So, I have a bacularis web container running. It appears I need something >> between the container and the director? but I cannot see what. >> >> regards >> >> Steven >> >> On Tue, 9 Apr 2024 at 05:17, Marcin Haba <ganius...@gmail.com> wrote: >> >>> 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 them" means that you can install Bacularis API in any way >>> that you want, Docker image is only one of the ways. >>> >>> Reading your description for that, what you would like to have, the >>> easiest is to install only one Bacularis using binary packages on the >>> Bacula Director host. It contains the Bacularis Web and Bacularis API >>> together, so you don't need to split it or install anything else, just this >>> one Bacularis instance. The installation wizard, that you will see after >>> installing, will lead you on all the configuration process. >>> >>> In case problems or questions, please let us know. Thanks! >>> >>> Best regards, >>> Marcin Haba (gani) >>> >>> On Mon, 8 Apr 2024 at 09:22, steven <ste...@graywitch.co.nz> wrote: >>> >>>> 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 >>>> years now. What I was hoping for was to have a web interface on top of >>>> Bacula. >>>> The docker container is running on the bacula director so it is local >>>> stuff. So I have to remove the bacula-director and add in the >>>> bacularis-api-dir instead? >>>> >>>> If I need to do serious alterations to the running setup, that is a >>>> step to far for me. >>>> >>>> >>>> regards >>>> >>>> Steven >>>> On 8/04/2024 7:07 pm, Marcin Haba wrote: >>>> >>>> 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 of each of these container images you can find in >>>> the "About this image" section in each of the Bacularis Docker Hub >>>> repositories. This description for the 'bacularis-web' container is the >>>> following: >>>> >>>> ==== >>>> 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. >>>> ==== >>>> >>>> The Bacularis Web to work needs at least one API host with bconsole and >>>> catalog access (and Bacula configuration capability if needed). So you can >>>> set up the Bacularis API in any way (installing binary packages, container, >>>> Composer, tar archives) and then connect it using the wizard from the >>>> bacularis-web container. >>>> >>>> Worth mentioning is that for the Bacula configuration part Bacularis >>>> API needs access to Bacula config files so easier is to work with Bacularis >>>> API instances outside the container. Otherwise you need to bind the Bacula >>>> configuration paths to Bacularis API container or use Bacula config files >>>> from Bacula in container. >>>> >>>> Your question also indicated me that this first step section needs to >>>> be better explained in the documentation. I will try to prepare it soon. >>>> >>>> Thanks! >>>> >>>> Best regards, >>>> Marcin Haba (gani) >>>> >>>> On Mon, 8 Apr 2024 at 07:16, steven <ste...@graywitch.co.nz> wrote: >>>> >>>>> 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 explanation of how to connect the >>>>> bacularis-web >>>>> docker container to an existing bacula setup ? >>>>> >>>>> >>>>> TY >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Bacula-users mailing list >>>>> Bacula-users@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/bacula-users >>>>> >>>> >>>> >>>> -- >>>> >>>> "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 >>>> >>> >>> >>> -- >>> >>> "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 >>> >> > > -- > > "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 > -- "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
