#apertus IRC Channel Logs

hello ??

good day

https://summerofcode.withgoogle.com/organizations/6567493276008448/

correct, but its my duty as org admin :)

funny facebook notification: "Your post "Attention: this page is being deleted by ...." is performing better than 95% of posts on that Page. Boost it for €27 to reach up to 123 more people daily."

might even go viral! :)

https://i.kym-cdn.com/photos/images/original/000/339/529/280.jpg

as the term "facebook" is used inside the text: "Your ad might not be approved We require ads featuring the Facebook or Instagram brand to follow specific brand guidelines because all Facebook and Instagram features and icons are legally protected brand assets. "

off for now ... bbl

lets make it go viral: https://cloud.gerade.org/index.php/s/Ji73XbAE9pJ8tRZ

I posted it also on our FB of course

good idea

https://imgur.com/a/2AEKqOw

hey! finally got the image : https://pasteboard.co/I36C04N.png

hi rohan_, very good

hi rohan_, great!

apertus has officially been listed as org for gsoc 2019 yesterday

repo is fine as you can also use it for the application later on

will talk soon!

BTW, congratulations for being accepted in GSoC! We're also in. :D

thanks for the report, reading

vup2, anuejn, what is the current state of git submodules in the firmware?

there are two submodules atm, one for the control daemon and one for the misc tools

the commit used is currently 4ea5116cef from 19.12.18

it can be updated already, as we have some improvements in the webui and daemon itself

the repo for the webui is https://github.com/apertus-open-source-cinema/web-remote right?

it uses npm to build final folder

a systemd unit to start it automatically would probably also be nedded, but that should be quite simple

lighttd would be good for now, also placing the content of dist folder there, to be able to call webui without further setup

what role does the devserver have?

for now yes, later we will replace it with socat, when webui will be self-contained app

you mean in the node setup?

"npm run build" should be sufficient to get "dist" folder, files there are final

ok so the devserver is not needed?

what is devserver?

socat would listen to some port and send self-contained app package to browser

why not use a real http server instead of socat?

ok

if we have webui in browser cache, then only wsserver is used for queries

why?

if the webui is in the browser cache it should also only use the wsserver for queries

self-contained app doesn'T need a webserver, which would reduce cpu usage and so on

i wouldnt bother

also a self-contained app still needs a webserver for initial load

was also thinking same before, then i'Ve read a bit on the net

but socat is then doing the same work a normal http server would do

we don't need a real webserver as no comms are done to it

yes but any non shitty webserver should be at 0% cpu usage if it gets no data

does the WSServer have a systemd unit already somewhere?

k

under what aspect?

i don't think so

regarding systemd, i think having the daemon also work without systemd would be quite nice

it is

systemd is only starting it, but you can use it also without, that's how i test usually

of course, as it uses sd-journal

we can also ditch systemd, then i would grab some small lib or create simple logger

on non systemd systems one could also just log to stdout and stderr and use rsyslog ore something

ok, will note it

all the best then, off for now

it's not a big problem to rework it, as the logging is not good yet and was on the list for review

nice

(but they are just special character sequences anyway)

in which case do we lose log levels?

*stderr

then there is only the error log and normal log output

yes sure

we only need one port (80) on the camera

but the a custom logger then would not have nice color highlights in the systemd log :)

and it gets a path assigned (ie. /backend or /api)

what setup does the webui currently expect?

npm for build

k

ok

do?

if you have questions just ask

okay will try to find time this we

regarding bumping the version of the control daemon and also the webui, i think it would be good in the future that whenever you have a stable / tested version of them to just open a pull request on axiom-beta-firmware which bumps the submodule commit

the process will contain PR from dev to master, afterwards PR from master to beta firmware repo

then development of the daemon could happen on the master branch

but when we are ready to provide real stable version of the firmware images, we will also probably need something like a testing branch

for the firmware?

maybe, but not now

not much work there, just a PR from dev to master

BAndiT1983: and a PR to the firmware whenever a version is tested / considerd stable

next update will follow soon

what happend to the problems with ninja?

*(without sensor)

ah okay so the problems are only with the beta at the hub?

ok

Hello Everyone !

I am computer science enthusiast , looking forward to contribute this organisation through GSoC

very good, which area are you generally interested in?

thank you !

Is there something important already discussed here ? because previous chats are not visible!

you should specify the area, as we have discussed a lot of different topics already

Any fix for it?

Y_G: could you upload the whole log (can be found under build/build.log) somewhere?

ah same xD

the build logs^

Thank you :)

vup anuejn please take a look at this PR: https://github.com/apertus-open-source-cinema/axiom-beta-firmware/pull/61

done

great, thanks

(the pr was a response to https://github.com/cirruslabs/cirrus-ci-docs/issues/172)