Skip to content
This repository has been archived by the owner on Sep 13, 2018. It is now read-only.

Latest commit

 

History

History
134 lines (70 loc) · 6.09 KB

README-pycharm.md

File metadata and controls

134 lines (70 loc) · 6.09 KB
Raw

Using PyCharm for ubersystem development

You can use anything you want to develop ubersystem.

We like https://www.jetbrains.com/pycharm/ for use as an IDE for a variety of reasons include ease of use for running unit tests, code completion/etc, debugging, etc.

Setup

Follow the setup instructions here first: https://github.com/magfest/simple-rams-deploy.

Make sure the virtual machine is running (use 'vagrant up' to bring it up).

Make sure you are running a recent version of PyCharm Professional 2016.2 or higher (not community edition)

  1. Open Pycharm

note: You are going to see some warning messages about 'can't find git version control roots' for a couple of projects, that's OK just ignore those. also dismiss anything about docker.

  1. File->Open and select the folder 'simple-rams-deploy' (or whatever you named it)

  2. File->Settings and under Project:rams, click Project Interpreter

  3. next to Project Interpreter, click the gear icon:

image

  1. Click 'Add Remote'

  2. Click the 'Vagrant' checkbox

  3. Under 'vagrant instance folder', select the subfolder in your project named 'ubersystem-deploy':

image

  1. The 'vagrant host URL field' should now switch automatically to 'ssh://vagrant@127.0.0.1:2222'

  2. For 'python interpreter path', either paste or browse to: /home/vagrant/uber/sideboard/env/bin/python3

  3. hit OK and exit the system settings. You may see some activity and messages of PyCharm working, this is normal and may take a minute or two to process.

One-time setup is now complete! Now you can do the following to debug in PyCharm

Anytime you restart vagrant, you will need to stop ubersystem from running in the background.

  1. In PyCharm, click Tools -> External Tools -> supervisorctl

image

This will stop ubersystem from running as a daemon and allow you to take control of it from PyCharm

Debugging in Pycharm

  1. In the upper right hand corner, click the dropdown that has the PyCharm configurations and select 'sideboard':

image

  1. Click the 'Debug' icon (it looks like a green bug)

You are now running ubersystem inside pycharm! You can set breakpoints and view the debug output.

Running Unit Tests in Pycharm

This is basically the same procedure as debugging.

  1. Select a unit test configuration:

image

  1. Click the 'Debug' icon to run the unit tests. You can set breakpoints inside the unit tests as well!

Source Control

All repositories (simple-rams-deploy, ubersystem-deploy, production-config, sideboard, and all plugins) show up at the same time and you can do most git operations from within pycharm. Click the 'version control' button at the bottom of the screen to explore. PyCharm is incredibly adept at dealing with having a complex setup of working on multiple repositories at the same time.

To update all of your projects from github:

  1. Click the bottom right source control dialog:

image

  1. Make sure everything is set to either 'master' or a branch that exists in github.

  2. Click the 'Update Project' button in the upper right to pull changes from github:

image

Re-deploying

If there are config changes introduced from github (this happens from time to time), or if you want to make sure you have the very latest, then follow this procedure to re-deploy. You'll need a decently fast internet connection as this process will pull down stuff from github/etc.

At some future point, we're going to make this process a bit more automated.

  1. First, follow the steps above in the 'source control' section to set all branches to master and update the project. (This is important because in order for the deploy to succeed, all of your local branches must correspond to branches that currently exist on github).

  2. Before deploying, make sure that any local changes are committed to source control or stashed (use the version control tab in PyCharm).

  3. Open a command prompt or terminal and change directory to simple-rams-deploy/ubersystem-deploy

  4. Run the 'vagrant up' command if the vagrant machine isn't already running.

  5. Run 'vagrant ssh' to ssh into the machine.

  6. Type 'cd ~/uber/puppet' then to deploy type './apply_node.sh localhost'. This will bring your deploy up to date with the latest code, apply all configuration (YAML/INI) changes, install any new plugins that were added, and a bunch of other stuff. It should end with a pristine copy of everything deployed and ready to rock.

  7. If you are planning on running the uber server from inside PyCharm (so you can debug it, for instance) then you'll need to turn off the server which the deploy auto-starts by typing 'sudo supervisorctl stop all' from inside vagrant. If not, skip this step.

Deploy is now finished! you can close the command prompt.

  1. If you were working on local changes, switch back to those branches, or unstash your changes.

  2. Click the 'debug' or 'run' icon in PyCharm and you should be up and running again.

To be continued

You can also do some other stuff we will document later like running with code coverage + unit tests to show you which lines of code are and aren't being hit.

Troubleshooting:

If you see 'Private key file not found' when setting up, please upgrade your PyCharm, there was a bug in older versions.

If things are in general starting to get weird, check that you have definitely clicked on the 'simple-rams-deploy' directory when you opened the project. If you open any other directory THINGS WILL START GETTING WEIRD.