search

balena-labs-projects / balena-cam

Network Camera with Raspberry Pi and WebRTC. Tutorial:
https://balena.io/blog/build-a-raspberry-pi-based-network-camera/
MIT License
175 stars 78 forks source link

Fleet configuration variables -- what is their purpose? #31

Closed drjasonharrison-vp-eio closed 5 years ago

drjasonharrison-vp-eio commented 5 years ago

What is the purpose of defining these variables in the fleet configuration? BALENA_HOST_CONFIG_start_x = 1 BALENA_HOST_CONFIG_gpu_mem_256 = 192 BALENA_HOST_CONFIG_gpu_mem_512 = 256 BALENA_HOST_CONFIG_gpu_mem_1024 = 448

Do they affect the HostOS, or all of the containers? Perhaps a link to https://www.balena.io/docs/learn/develop/hardware/i2c-and-spi/#raspberry-pi-camera-module

would be helpful

mbalamat commented 5 years ago

@drjasonharrison-vp-eio If I get your question right on why we add these variables in the fleet configuration tab is because on balena-cloud I have an app called myHomeCams and if I want to add more devices on this app (essentially more cameras) I don't want to set up these variables for every new device that I add, so the reason is convenience, of course you can set them per device but it's more convenient using fleet wide variables. Regarding your second question it's the way to access the hardware of the device as you correctly pointed to the docs.

If you have any other questions let me know!