ann0see/rasjam

Setup a Jamulus infrastructure with Raspberry Pi clients

RasJam

Currently in planning phase. This project has the goal to manage and setup multiple Raspberry Pis using Jamulus from a central server. This is mainly for large groups wanting to jam together and needing a simple setup.

What should be done? (Suggested workflow)

1. Setup Jamulus and admin server
2. Compile Jamulus with a script
3. Move the copyToStick folder to a stick
4. Burn multiple raspbian light SDs
5. Connect the stick to all the raspis
6. Run a script from the stick
7. After all the raspis, upload SSH keys to the server

Thoughts:

• One person (admin) sets up a jamulus server to which all clients (Raspis) connect to.
• All Raspberry Pis reverse ssh into the server to allow the admin to update/... the clients (script exists)
• All Raspberry Pis run a headless (?) build of jamulus client which is somehow locally controlled (not yet possible/moved away) (webbrowser, MIDI controller,...) --> we use a small (touch) screen
• All Raspberry Pis automatically start jamulus and connect to the server if switched on (todo: autostrat)
• All Raspberry Pis are centrally managed e.g. via ansible/ Updates: own apt repo?
• During setup phase admin executes a script on every pi which sets up jamulus and the ssh tunnel and gets the ssh key of the raspi (done)
• Passwords are saved in plain text on the USB Stick. What about security?
• Integrate an update API (authenticated. Maybe via PHP?)
• What should we do with the ssh key signature of the api server (see sshAccess/startReverseSSHTunnel.sh)? Can we just trust anything???
• On SSH-Key update on server we must send a update message to all the clients

rasjam's Issues

Further ideas and development

@gene96817

I saw that you follow me and watch this repo. Furthermore you also created a repo which has a similar idea. Do you want to contribute/have ideas? I'd be happy to have someone else in my team ;-).

Thinking about the client hardware

In exploring this repository, it seems you have decided that all musicians/clients will use RPi.

What led to the conclusion not to use any Mac or Windows machines that the musician already owns?
I do agree that Window's users are very difficult to onboard to Jamulus. The audio interface issue stumps most Windows users.

What about musicians that have high-quality mics and audio-interfaces?
Are you expecting the musicians to only use USB mics with the RPi?

I am looking for people that have experience running Jamulus on Chromebooks. A lot of public schools around here have given students Chromebooks. I don't have any experience (yet) on this. I need a lot of help on this.

Include server management

Currently the client-side works.

The server side is not yet finished because it's not yet clear if it should be managed via reverse ssh (privacy problems) or unattended-upgrades (happens every now and then. Might disturb jamulus sessions). Already setup unattended-upgrades.