since runbuilds is run by a script (or service file) adding an env variable to the sample is another way to address this for a production setup. from the wiki:
#!/bin/sh # toaster run builds dispatcher cd /var/www/toaster/ source ./venv/bin/activate export BITBAKE_UI='toasterui' while true; do ./poky/bitbake/lib/toaster/manage.py runbuilds; sleep 3; done -b an intel employee On Tue, Mar 8, 2016 at 7:25 AM, Michael Wood <[email protected]> wrote: > On 07/03/16 19:00, Ed Bartosh wrote: >> >> Set BITBAKE_UI variable to 'toastergui' for command line builds >> to use toasterui as a default ui module for bitbake. >> >> Signed-off-by: Ed Bartosh <[email protected]> >> --- >> bitbake/bin/toaster | 2 ++ >> 1 file changed, 2 insertions(+) >> >> diff --git a/bitbake/bin/toaster b/bitbake/bin/toaster >> index 1e6e690..5cc77ed 100755 >> --- a/bitbake/bin/toaster >> +++ b/bitbake/bin/toaster >> @@ -100,6 +100,7 @@ stop_system() >> unset DATABASE_URL >> unset TOASTER_CONF >> unset TOASTER_DIR >> + unset BITBAKE_UI >> trap - SIGHUP >> #trap - SIGCHLD >> INSTOPSYSTEM=0 >> @@ -259,6 +260,7 @@ case $CMD in >> echo "Failed ${CMD}." >> return 4 >> fi >> + export BITBAKE_UI='toasterui' >> export DATABASE_URL=`$MANAGE get-dburl` >> $MANAGE runbuilds & echo $! >${BUILDDIR}/.runbuilds.pid >> # set fail safe stop system on terminal exit > > > We want to avoid having anything that is required for Toaster to run only in > /bin/toaster as Toaster needs to be able to work without running > /bin/toaster in the production set up. > > > -- > _______________________________________________ > toaster mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/toaster -- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
