Skip to main content

Workspace

Similar to git and other tools, RemotiveTopology use a hidden folder .remotive to store workspace information. The data in this folder is just cache data to improve performance and can be deleted to save space. Typically you shouldn't include all files in .remotive in version control.

Using a workspace​

To initialize the workspace

cd remotivelabs-topology-examples
remotive topology workspace init

Now all commands running in any subdirectory use the same workspace, for example:

cd remotivelabs-topology-examples/remotive_car
remotive topology show topology instances/hello_world/main.instance.yaml --resolve

If you are unsure which folder is the current workspace, try:

remotive topology workspace current

Without workspace​

When running RemotiveTopology without a workspace the current working directory is considered as a temporary implicit workspace. This is useful when running some quick commands without creating temporary files. However, using an initialized workspace is normally faster due to the caches.

When running outside a workspace:

  • Don't use absolute paths
  • Don't use ..

Windows​

Make sure to use WSL2 when using RemotiveTopology! Many RemotiveCLI commands works in PowerShell, but not RemotiveTopology.