584
edits
Changes
Jump to navigation
Jump to search
Line 36:
Line 36: + − + Line 61:
Line 62: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
→Setting up Remote Deployment
Make sure you have a working zynthian first ...
Make sure you have a working zynthian first ...
If you don't have a MIDI keyboard to hand you can used qmidinet(on linux) and it's windows equivalent (ipMIDI http://nerds.de) to connect from a host machine to the zynthian and then use a virtual keyboard (VMPK on linux, don't know about windows) to operate the zynthian . . .
== Setting up Pycharm ==
== Setting up Pycharm Project ==
1. Create a new, blank PyCharm project. Call it Zynthian.
1. Create a new, blank PyCharm project. Call it Zynthian.
9. If you haven’t already, go to Tools->Deployment->Configuration. Set it up like this:
9. If you haven’t already, go to Tools->Deployment->Configuration. Set it up like this:
[[File:Pycharm-zynth-deployment.png]]
10. You can then set up the mappings between the projects and the Zynthian directories in the same dialog:
[[File:Pycharm-zynth-deploy2.png]]
== Setting up Remote Deployment ==
PyCharm handles remote file systems with the deployment feature this is one of the features that is only in the paid edition. Such is marketing . . .
You define a relationship between the local file structure on the local machine and a file structure on the remote machine which in our case will be maintained over ssh. You can set it up so that files that are changed in the local environment where you would edit, are auto-majically copied to the remote directory. Also you can used the Right Hand click on a Project object (file, directory or whole project).
[[File:Pycharm Projects.png]]
This allows a pretty fine granularity of deployment and copying both ways which is handy.
To set it up we have to venture into the wonderful world of PyCharm settings [File | Settings...| Build Execution Deployment | Deployment]
[[File:Pycharm-zynth-Deployment-setup.png]]
'''Connection Tab'''
''Name''
The first thing to do is come up with a decent name for this deployment instance. The reason being you will pick this definition up in other functions and it's very easy to get confused with exactly which configuration you are relating to which.
''Type''
Choose SFTP
''SFTP host''
Use the zynthian local name you have chosen in the webconf (avoid IP addresses at all costs that way lies madness)
so zynthian.local
''Port''
Leave at 22
''Root Path ''
I'm finding leaving this as / avoids all kinds of involved directory mappings at a later date.
''User name''
root in the zynthian world.
The rest are pretty self explanatory . . .
'''Mapping Tab'''
[[File:Pycharm-zynthian-deployment-settings=mapping.png]]
''Local path''
This points to the root of the local file structure.
''Deployment path on ....''
The Deployment location on the remote device relative to the root we defined in the Connection tab.
''Web Path on ....''
Just put in /
This gives you a deployment mapping and if you return to the connections tab you can test the connection. Make sure this works before you go any further.
The trick with the remote debug is to define a remote Interpreter.
imageimage.png1030x714 46 KB
The Little cog wheel has a Show All option which is a bit non intuitive and is often used during the initial confusions.
However we want the Add Menu Option.
Which gives us
imageimage.png843x617 36.4 KB
Select the ssh option . . .
imageimage.png842x578 25.5 KB
and fill all that in . . .
imageimage.png858x578 21.5 KB
and that. . . .
**AND THEN SET THE INTERPRETER TO python3 in the following **
imageimage.png838x573 23.5 KB
Hey Presto All the code loaded on the remote pi !!
imageimage.png1030x705 79.9 KB