-
Notifications
You must be signed in to change notification settings - Fork 95
NOS3 Workflows
Two workflows are common to utilize NOS3 as a user / developer: 1. Solely in the VM (git clone within the VM) 2. Develop on host machine, test in VM (git clone on the host, share the git folder into the VM)
Both options make use of the vagrant virtual machine to provide a stable environment for testing. If using vagrant (`vagrant up`), the VM will have the source code folder shared into the VM as `/home/nos3/Desktop/github-nos3`. If using Virtual Box to start the VM, the source code can be cloned into a location of your choosing in the VM via `git clone https://github.com/nasa/nos3`. If using Virtual Box to start the VM, the source code can be shared into the VM using the following directions: 1. Go to Virtual Box menu -> Devices -> Shared Folders -> Shared Folders Settings... 2. Add a new Shared Folder (folder with + sign) and select the location of the nos3 repository on the host 3. Check `Auto-mount` and `Make Permanent` 4. Reboot the VM
Once these steps are complete, all changes inside will be reflected outside and vice versa.
- Home
- NOS3 Architecture
- NOS Engine
- NOS3 Ground Systems
- NOS3 Install, Build, Run
- NOS3 Components, Repository and Directory Structure
- NOS3 Running Executables and Windows
- NOS3 Workflows
- NOS3 Hardware Simulator Framework / Example Simulator
- NOS3 42 Orbit and Attitude Dynamics
- NOS3 cFS Development
- NOS3 Component Directory
- NOS3 Component Development Flow
- NOS3 Custom cFS Table Development
- NOS3 OIPP
- CryptoLib
- NOS3 Igniter