This repository contains the configuration of the Eagle Enterprises Development Environment used for building UAV Simulation and Training Environments.
If there is anything wrong with this repository (documentation needed / broken things), please use the Bug Template to report the issue
-
Vagrant: 2.4.1
After installing vagrant, restart the device, then install these vagrant plugins:
- vagrant-hostmanager
vagrant install vagrant-hostmanager
- vagrant-vboxguest
vagrant plugin install vagrant-vbguest
- vagrant-hostmanager
-
VirtualBox: 7.0.8
-
git: version 2.41.0.windows.2
-
Integrated Development Environment (of your choice)
-
Install Dependencies Listed Above
-
Clone this repository to a folder on your personal computer
-
Run the following command from within the cloned repository (i.e.
/eagle-development-environment/):vagrant up -
Wait for the Vagrant Command to bring up the Virtual Machine
-
It may take a few minutes, depending on your machine and internet connectivity
-
Time snapshot of mine
- real 2m32.230s
- user 0m0.000s
- sys 0m0.016s
-
For example, one machine was ready after the terminal showed the following message:
VirtualBox Guest Additions: Building the modules for kernel 6.5.0-21-generic. update-initramfs: Generating /boot/initrd.img-6.5.0-21-generic VirtualBox Guest Additions: Running kernel modules will not be replaced until the system is restarted or 'rcvboxadd reload' triggered VirtualBox Guest Additions: reloading kernel modules and services VirtualBox Guest Additions: kernel modules and services 7.0.14 r161095 reloaded VirtualBox Guest Additions: NOTE: you may still consider to re-login if some user session specific services (Shared Clipboard, Drag and Drop, Seamless or Guest Screen Resize) were not restarted automatically
-
-
Bring up the VirtualBox UI and click the
eagle-development-environmentVM. -
Login to the Virtual Machine
- uname:
vagrant - password:
vagrant
- uname:
Note You can alter the vb.memory value in the Vagrantfile based on how much RAM your personal machine has. I wouldn't give it more than %50 of what your system max is
- To start the machine run the following command from within the directory of
this cloned repository (i.e.
/eagle-development-environment/):vagrant up - To open Mission Planner:
- Open the Terminal
- Click on the "Show Apps" (grid) button on the lower left corner, which will display the apps menu.
- Use the search bar at the top to search for "Terminal".
- Click on the resulting option.
- Type in /opt/MissionPlanner/MissionPlanner.exe into the terminal.
- To shutdown the virtual machine, run the following command on a new terminal
in VS Code:
vagrant halt. Virtual Box should show the machine in a "Powered Off" state.
- To open Mission Planner in the VM use the following command:
sudo mono /opt/MissionPlanner/MissionPlanner.exe
git clone <url> -------------------- Clones a git repository. URL can be found
by clicking the green code button on the repository webpage
git status ------------------------- Shows you the status of your local
vagrant up -------------------------------- Brings up the Virtual Machine
according to the Vagrantfile in the Working Directory
vagrant ssh ------------------------------- Secure Shell into the Virtual
Machine
vagrant halt ------------------------------ Brings down the Virtual Machine
according to the Vagrantfile in the Working Directory DO THIS BEFORE SHUTTING
DOWN YOUR MACHINE
vagrant reload ---------------------------- Will reload the Virtual Machine (
can pass it --provision or --no provision to force it to be provisioned,
which means it will install all dependencies)
vagrant destroy --------------------------- Will destroy the Virtual Machine
to be brought up with another vagrant up Any work not saved in the
/vagrant directory will be lost
This is completely optional, just if you're curious as to which I'm using:
-
In Bash:
cat vs-code-extensions-list.txt | xargs -L 1 code --install-extension -
In PowerShell: Get-Content vs-code-extensions-list.txt | ForEach-Object { code --install-extension $_ }
- It has been found that VirtualBox does not operate correctly in Mac PCs with an M1 chip. For more information please visit this Reddit Thread.
- If an error occurs in GitHub or in your code editor such as "Sorry, you're not able to edit this repository directly -- You need to fork it and propose changes from there instead", please ask access to the repository by sending a direct message via Discord to the repository owner. Once access has been granted by the owner, an email will be sent with an invitation to email linked to your GitHub account. Please click the "Accept Invitation" button on the email. This should resolve the issue.
- If you just installed Vagrant, the device on which it was installed will need to be restarted before the software is usable.
- Otherwise, please repair vagrant by opening the installer and clicking "Next" > "Repair".
- You can also try to reinstall vagrant
- The time that the vagrant takes to load the virtual machine is heavily dependent on your machine's hardware. It can definitely take much longer than expected.
- Make sure your machine has at least 4 MB available of RAM (memory) to provide to the Box. If your machine has less than that, modify the vagrant file vb.memory value to be less than 50% of your machine's RAM.
- For windows, follow these instructions. You may need to click aditionally on "Change high DPI settings". Then, shut down the VM as per the VM Usage Guide and restart VirtualBox.
- Ensure the VM has at least 4 processors.
- Make sure the VM is off.
- Go to VBox and select the "Settings" of the VM.
- Go to System > Processor.
- Change the number of processors to a more appropriate number.
- To get any repos into the VM, please clone them in the
/eagle-development-environmentdirectory corresponding to this repository on your host system (where the vagrant file is). The repository directories copied there will be bidirectionally synced to the VM.
- The developer environment VM is local to each host device.
