Provisioning

Provisioning your Raspberry Pi on resin.io

• Sign up for a resin.io account

• Create a new resin.io application to manage your Boombeastic. It can be a starter or microservices type

• Add SSH key

  • More detailed information about the application creation process (including adding a SSH key) is available in the resin.io getting started guide and create a new Raspberry Pi zero or Raspberry Pi 2/2+/3 application (depending on what Raspberry Pi you have). Name this application whatever you want, e.g. BoombeasticMini.

• clone this repository to your local system and open up the Boombeastic project by pasting the following into a terminal¹: git clone https://github.com/resin-io-projects/boombeastic cd boombeastic

• set these variables in the Fleet Configuration application side tab

  • RESIN_HOST_CONFIG_dtoverlay = "hifiberry-dac","i2s-mmap"
  • RESIN_HOST_CONFIG_dtparam = "i2c_arm=on","spi=on","audio=off"

• add the resin remote to your local workspace using the useful shortcut in the dashboard UI. Copy and paste the line from the top of your application page into a terminal and run it.

• In your terminal run git push resin master.

If you have not pushed code to resin.io before, you may see something like the following:

Warning: Permanently added 'git.resin.io,54.165.162.194' (ECDSA) to the list of known hosts.


The authenticity of host 'git.resin.io (54.165.162.194)' can't be established.
ECDSA key fingerprint is SHA256:NfwmqnKId5cx1RWpebbEuuM87bCJbdyhzRnqFES9Nnw.
Are you sure you want to continue connecting (yes/no)?

Don't worry! This is normal and just a security precaution before pushing code for the first time. Just type yes and press enter. (You won't see this message for subsequent git push commands.)

• see the magic happening, your device is getting updated over-the-air (OTA)!

After the OTA is completed, you can test the connection by pointing your browser to your BoomBeastic IP¹

¹ You can read about how to retrieve your BoomBeastic IP here