You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One thing I was thinking whilst doing #194 was that we could do a similar thing with mlat-client container as was done with the autohupr container.
In other words, have it uncommented in the docker-compose.yml but disabled by default. And then, like autuhupr container, we could enable it by adding the name to the ENABLED_SERVICES device variable.
This would have the disadvantage of meaning that container was built for every device (using up an extra ~220MB of disk space. But it would make it easier for people to enable it and use it without having to fork the repo and manually deploy.
Essentially, they would be able to use it by just using deploy with balena and setting some device variables.
I think now that we have such feature, it could make sense, with the same auto shutdown enabled.
shawaj
changed the title
potentially move mlat-version to an "ENABLED_SERVICES" type arrangement?
potentially move mlat-client to an "ENABLED_SERVICES" type arrangement?
Jan 4, 2025
One thing I was thinking whilst doing #194 was that we could do a similar thing with
mlat-client
container as was done with theautohupr
container.In other words, have it uncommented in the docker-compose.yml but disabled by default. And then, like
autuhupr
container, we could enable it by adding the name to theENABLED_SERVICES
device variable.This would have the disadvantage of meaning that container was built for every device (using up an extra ~220MB of disk space. But it would make it easier for people to enable it and use it without having to fork the repo and manually deploy.
Essentially, they would be able to use it by just using deploy with balena and setting some device variables.
Not sure what you think @Teko012 @ketilmo ?
The text was updated successfully, but these errors were encountered: