Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

potentially move mlat-client to an "ENABLED_SERVICES" type arrangement? #198

Open
shawaj opened this issue Jan 3, 2025 · 1 comment
Open

Comments

@shawaj
Copy link
Collaborator

shawaj commented Jan 3, 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 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.

Not sure what you think @Teko012 @ketilmo ?

@Teko012
Copy link
Collaborator

Teko012 commented Jan 3, 2025

I think now that we have such feature, it could make sense, with the same auto shutdown enabled.

@shawaj 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants