how to start add feature to tinypilot

Thanks for reaching out!

Is there any documentation where to put files on tinypilot for the scripts?

We don't document it, but it should be straightforward to find where a file lives by looking at where similar files currently live.

• Python files live here: https://github.com/tiny-pilot/tinypilot/tree/master/app
• Shell scripts (including those that require root) live here: https://github.com/tiny-pilot/tinypilot/tree/master/debian-pkg/opt

We do have documentation here:

• https://github.com/tiny-pilot/tinypilot/blob/master/CONTRIBUTING.md

• https://github.com/tiny-pilot/tinypilot/blob/master/ARCHITECTURE.md

Is it breaking the law if it will need redis installed?. I will need it since I will use RS232 to communicate to managed nodes. so it will single threaded. need kind of queueing system to anticipate operational request.

Is it breaking the law if it'll need tinypilot to have and import additional python modules (i.e: celery)

It's not breaking TinyPilot rules, but we also wouldn't be accepting changes that add power control into the main codebase. We can help you manage your own fork and point people to it when they request power control, but we don't have the bandwidth to support power control features.

That said, adding redis and celery for this seems like overengineering. Wouldn't you basically just need the TinyPilot to turn a Pi GPIO pin on or off? Why would that require a whole separate queue and processing module? Turning on a GPIO pin takes a few milliseconds, so it's not going to lock up the main thread. Even if it did, you could do it with Python's native subprocess module like we do already for background tasks:

https://github.com/search?q=repo%3Atiny-pilot%2Ftinypilot%20subprocess&type=code