…started

… gisnav services, not other services

…-compose service

…v-compose Debian package

…pped and only remove them when the package is removed

Copies over ROS package source code so that the .deb package can build the gisnav image on its own. Makes the
package independent of any external container registry.

Disables running px4 service by default (introduces docker-compose.companion.yaml override) as it is not intended
to be run on the companion computer where gisnav-compose is intended to be installed.

Makes postrm script more robust to missing files, missing commands etc.

Includes dummy docs folder and vitepress/package.json to ensure gisnav image Dockerfile script goes through.

Uses .gitignore to ensure rsync does not copy over unintended files to the Debian package

…script

Fix fileserver build by removing unneeded firefox browser

Create containers in addition to just building them

Remove old link to old Jetson Nano article from VitePress docs

…ted colcon package)

…rary swapfile if needed

…ow overriding the depends_on key as an exception

… setup for different GPU manufacturers

…dia override

This is needed because the (Nvidia) device reservation cannot be overridden if made default

…use of the new CLI

…tead of as a volume in docker-compose.broadcom.yaml override

…nability

…and pull information (i.e. how to actually obtain the images) in the base compose file

…l Makefile

…directory was introduced

…sages more visible

…itors/readers

Introduces a physical split between the simulation host and companion computer in preparation of supporting HIL deployments

The compose file has been split into too many files to specify manually and a script is now used to build to stack of Compose overlays

We use prepare instead of setup because setup is often conflated with install which we have already done.

Makes error message more explicit when various required env variables are empty or not defined.

This helps with not having to think about choosing which docker compose overlay configurations and which services to deploy

…borders

…ame host

…guration files

These files should not be needed but are still kept in the repo for future reference

…me on install

Because of the timestamped build ID we either had to call clean or make it a .PHONY target earlier to prevent loading up the dist folder with old Debian packages

…oded installation path

This makes the script useful also for development - documentation updated to reflect this

…age)

- uXRCE port passed as host to uxrce_dds_client start
- use of localhost where host.docker.internal was intended
- remove ugly uxrce_dds_client restart by editing the rcS file instead using sed
- remove ROS middleware from mavlink network which now is physically separate
- use environment variables instead of hard-coded values for ports in compose config files wherever appropriate
- open (currently hard-coded) port 5600 for UDP video for gscam service

Gets around problems around shared memory transport between Docker containers (more info in dds network description label and updated docs)

With px4 we need to use the host network because the uXRCE-DDS bridge seems to use ephemeral ports for inbound communication (SensorGps message) - unverified

Ideally they simulator and QGC would still be in a dedicated mavlink network

…is passed onto docker compose

This significanly reduces the functionality of the tool while at the same time reducing amount of maintainable code

…able e.g. on raspberry pi by default)

Now understands localhost and 127.0.0.1 are not remotes and will not use ssh.

Correctly runs services on localhost if mixed with services running on remotes.

Correctly runs when no services are specified, whether on local or remote.

Correctly runs when local services are given while no services are given for remote (i.e. gnc stop px4 @remotehost).