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

Move scripts API to uavos/apx-fw #75

Open
uavinda opened this issue Apr 18, 2024 · 0 comments
Open

Move scripts API to uavos/apx-fw #75

uavinda opened this issue Apr 18, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@uavinda
Copy link
Member

uavinda commented Apr 18, 2024

The whole scripts dev environment should be moved from GCS resources to uavos/apx-fw repo as module and generate apxfw with resources, latter copied and extracted by GCS as other firmware metadata.

The goal is to each node to have separate script dev environment embedded in apxfw file as other metadata. When GCS user edits a script - GCS copies dev env from corresponding apxfw. Thus, allowing each node to have its own API with fallbacks to older versions and other nodes (f.ex. nav).

@uavinda uavinda added the enhancement New feature or request label Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant