raspiblitz/alternative.platforms/amd64/README.md

# ⚡️ RaspiBlitz-on-amd64 ⚡️

This guide was tested on vagrant

---

This feature is very experimental and not supported.

In order to run raspiblitz on `vagrant` you need `packer` (>=1.6.0) to build the base box.

On MacOS you need to install:
1. brew: `/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"`
2. packer: `brew install packer`
3. vagrant: `brew install vagrant`
4. virtualbox: `brew cask install virtualbox` (maybe re-run after you changed the requested security permission to be successful)

```
cd alternative.platforms/amd64/packer
packer build raspiblitz.json
vagrant box add --force rotzoll/raspiblitz output/raspiblitz.box
cd ../../..
```

With the base box built, you can start a development environment with `vagrant up` and login with `vagrant ssh`.

You will need to connect a virtual data drive to the RaspiBlitzVM ... todo so:
- make sure VM is stopped: use command `off` when within VM or from outside `vagrant halt`
- no open the VirtualBox Manager GUI and use `change` on the RaspiBlitzVM
- Go to the `mass storage` section and add a second disc as `primary slave` to the already existing controller
- Use the [torrent-downloaded VDI](https://raw.githubusercontent.com/rootzoll/raspiblitz/dev/alternative.platforms/amd64/raspiblitzHDD.vdi.torrent) file or create a new dynamic VDI with around 900GB .. choose as storage path for the VDI an external drive if you dont have that much space on your laptop.
- now start the VM again with `vagrant up` and `vagrangt ssh` to run thru the setup process

**Note**

Every file in `home.admin` will be linked to `/home/admin` inside the VM,
if you add a new file you should run `vagrant provision` to make sure it gets linked inside the VM. Every time you boot the VM, `home.admin` files will be linked automatically.

The content of the `/home/admin/assets` folder is not kept in sync at the moment (see [#1578](https://github.com/rootzoll/raspiblitz/issues/1578)). You can still access your development assets file inside the VM in `/vagrant/home.admin/assets/`.
Add vagrant support (#1523) This will allow building a raspiblitz base image with packer and spin up a development environment in a VM. 2020-09-23 13:28:18 +02:00			`# ⚡️ RaspiBlitz-on-amd64 ⚡️`

			`This guide was tested on vagrant`

			`---`

			`This feature is very experimental and not supported.`

Vagrant: Updates for MacOS & Packer >1.6.0 (#1657) 2020-10-13 22:25:35 +02:00			In order to run raspiblitz on `vagrant` you need `packer` (>=1.6.0) to build the base box.

			`On MacOS you need to install:`
			1. brew: `/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"`
			2. packer: `brew install packer`
			3. vagrant: `brew install vagrant`
Typo fixes (#2360) 2021-08-27 03:59:21 -04:00			4. virtualbox: `brew cask install virtualbox` (maybe re-run after you changed the requested security permission to be successful)
Add vagrant support (#1523) This will allow building a raspiblitz base image with packer and spin up a development environment in a VM. 2020-09-23 13:28:18 +02:00
Optimize Vagrant Mode #1579 (#1665) 2020-10-14 01:31:27 +02:00			```
Add vagrant support (#1523) This will allow building a raspiblitz base image with packer and spin up a development environment in a VM. 2020-09-23 13:28:18 +02:00			`cd alternative.platforms/amd64/packer`
			`packer build raspiblitz.json`
Optimize Vagrant Mode #1579 (#1665) 2020-10-14 01:31:27 +02:00			`vagrant box add --force rotzoll/raspiblitz output/raspiblitz.box`
Add vagrant support (#1523) This will allow building a raspiblitz base image with packer and spin up a development environment in a VM. 2020-09-23 13:28:18 +02:00			`cd ../../..`
			```

			With the base box built, you can start a development environment with `vagrant up` and login with `vagrant ssh`.

Vagrant: Updates for MacOS & Packer >1.6.0 (#1657) 2020-10-13 22:25:35 +02:00			`You will need to connect a virtual data drive to the RaspiBlitzVM ... todo so:`
			- make sure VM is stopped: use command `off` when within VM or from outside `vagrant halt`
			- no open the VirtualBox Manager GUI and use `change` on the RaspiBlitzVM
			- Go to the `mass storage` section and add a second disc as `primary slave` to the already existing controller
#1670 vdi image torrent & doc (#1716) 2020-10-26 12:50:16 +01:00			`- Use the [torrent-downloaded VDI](https://raw.githubusercontent.com/rootzoll/raspiblitz/dev/alternative.platforms/amd64/raspiblitzHDD.vdi.torrent) file or create a new dynamic VDI with around 900GB .. choose as storage path for the VDI an external drive if you dont have that much space on your laptop.`
Vagrant: Updates for MacOS & Packer >1.6.0 (#1657) 2020-10-13 22:25:35 +02:00			- now start the VM again with `vagrant up` and `vagrangt ssh` to run thru the setup process
Add vagrant support (#1523) This will allow building a raspiblitz base image with packer and spin up a development environment in a VM. 2020-09-23 13:28:18 +02:00
			`Note`

			Every file in `home.admin` will be linked to `/home/admin` inside the VM,
			if you add a new file you should run `vagrant provision` to make sure it gets linked inside the VM. Every time you boot the VM, `home.admin` files will be linked automatically.

Optimize Vagrant Mode #1579 (#1665) 2020-10-14 01:31:27 +02:00			The content of the `/home/admin/assets` folder is not kept in sync at the moment (see [#1578](https://github.com/rootzoll/raspiblitz/issues/1578)). You can still access your development assets file inside the VM in `/vagrant/home.admin/assets/`.