-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
366 add cli commands to inspectrestart the environment (#409)
Co-authored-by: David Perl <david.perl@diamond.ac.uk> Co-authored-by: Callum Forrester <callum.forrester@diamond.ac.uk>
- Loading branch information
1 parent
31c94c5
commit 6a9efe1
Showing
8 changed files
with
311 additions
and
29 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,23 +1,28 @@ | ||
# Run/Debug in a Developer Environment | ||
# Run/Debug in a Developer Environment | ||
|
||
Assuming you have setup a developer environment, you can run a development version of the bluesky worker. | ||
|
||
|
||
## Start Bluesky Worker | ||
|
||
Ensure you are inside your virtual environment: | ||
``` | ||
|
||
``` | ||
source venv/bin/activate | ||
``` | ||
|
||
You will need to follow the instructions for setting up ActiveMQ as in [run cli instructions](../how-to/run-cli.md). | ||
|
||
You will need to follow the instructions for setting up ActiveMQ as in [run cli instructions](../how-to/run-cli.md). | ||
|
||
The worker will be available from the command line (`blueapi serve`), but can be started from vscode with additional | ||
The worker will be available from the command line (`blueapi serve`), but can be started from vscode with additional | ||
debugging capabilities. | ||
|
||
1. Navigate to "Run and Debug" in the left hand menu. | ||
2. Select "Worker Service" from the debug configuration. | ||
3. Click the green "Run Button" | ||
|
||
[debug in vscode](../images/debug-vscode.png) | ||
|
||
## Develop devices | ||
|
||
When you select the 'scratch directory' option - where you have devices (dodal) and plans (BLxx-beamline) in a place like `/dls_sw/BLXX/software/blueapi/scratch`, then the list of devices available will refresh without interfacing with the K8S cluster. Just run the command `blueapi env -r` or `blueapi env --reload`. | ||
|
||
With this setup you get a developer loop: "write devices - write plans - test them with blueapi". |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.