Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix the instructions for connecting to XFELs broker offline #20

Merged
merged 1 commit into from
Jul 7, 2023
Merged

Fix the instructions for connecting to XFELs broker offline #20

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ at the command line.
## Kafka
The GUI is updated by Kafka messages sent by the backend. Currently we use
XFEL's internal Kafka broker at `exflwebstor01.desy.de:9102`, but this is only
accessible inside the control network.
accessible inside the DESY network.

DAMNIT can run offline, but if you want updates from the backend and you're
running DAMNIT outside the network and not using a VPN, you'll first have to
Expand All @@ -50,7 +50,14 @@ forward the broker port to your machine:
ssh -L 9102:exflwebstor01.desy.de:9102 max-exfl.desy.de
```

And then set the `AMORE_BROKER` variable:
And then add a line in your `/etc/hosts` file to resolve `exflwebstor01.desy.de`
to `localhost` (remember to remove it afterwards!):
```
127.0.0.1 exflwebstor01.desy.de
```

And then DAMNIT should be able to use XFELs broker. If you want to use a specific
broker you can set the `AMORE_BROKER` variable:
```bash
export AMORE_BROKER=localhost:9102
```
Expand Down