I had a look at the code, and the address appears to be hard coded for localhost, i.e.127.0.0.1
I have a pi running sonic-pi, and a separate Linux LMDE PC running JupyterLab.
I know I can change the code to address my Pi, and pretty certain that would work, but it would be nice to have an option.
p.p. I tried editing the server code, it doesn't work as I thought. I believe that sonic running as a server using command
/opt/sonic-pi/app/server/ruby/bin/sonic-pi-server.rb
has an issue itself. I haven't got the sonic-pi-tool running yet...
I haven't managed to figure out if it is the wrong port, or that it isn't actually listening outside of localhost. Will continue investigating. For the moment, I have jupyter running locally, and your interface is very nice. Looking forward to the supercollider version.... I bet that is a lot more difficult. I am currently accessing supercollider via node-red and node-red-contrib-music which may be of some interest.
I had a look at the code, and the address appears to be hard coded for localhost, i.e.127.0.0.1
I have a pi running sonic-pi, and a separate Linux LMDE PC running JupyterLab.
I know I can change the code to address my Pi, and pretty certain that would work, but it would be nice to have an option.
p.p. I tried editing the server code, it doesn't work as I thought. I believe that sonic running as a server using command
/opt/sonic-pi/app/server/ruby/bin/sonic-pi-server.rb
has an issue itself. I haven't got the sonic-pi-tool running yet...
I haven't managed to figure out if it is the wrong port, or that it isn't actually listening outside of localhost. Will continue investigating. For the moment, I have jupyter running locally, and your interface is very nice. Looking forward to the supercollider version.... I bet that is a lot more difficult. I am currently accessing supercollider via node-red and node-red-contrib-music which may be of some interest.