Set up for remote work

This remote work guide describes a setup in which your local machine will act as a thin client to your machine in the office, allowing you to edit code and access hosted instances. You will need VPN access to Seqpipe’s internal network and ssh. Additionally, if you use VSCode or a non-terminal-based editor you will have to set that up as well, either through inbuilt SSH functionality or via sshfs. VSCode documentation online provides information on how to set it up.

  1. Set up the VPN connection to the office. You will need credentials (if you have none or have lost yours, ask in the Zulip chat). Follow the guide provided in the seqpipe-infrastructure repository here.

  2. Test your VPN connection by pinging the machine you wish to connect to. If pinging with machinename.local doesn’t work, you’ll need the machine’s IP (see the table below). If nothing works, ask for help in the Zulip chat.

  3. SSH into your machine. To avoid having to open up multiple ssh connections for each terminal you need, use tmux.

  4. Go to gpf and edit the CORS_ORIGIN_WHITELIST variable in wdae/wdae/wdae/settings.py to include the IP address of your machine (with port 4200 of the Angular dev server):

    CORS_ORIGIN_WHITELIST = [
    "http://10.0.2.253:4200",
]

  5. Go to gpfjs and change the basePath variable in src/environments/environment.ts to the IP address of your machine (with port 8000 of the Django dev server):

    const basePath = 'http://10.0.2.253:8000';

  6. Run the gpf and gpfjs servers with the following commands:

    • wdaemanage.py 0.0.0.0:8000

    • ng serve --host 0.0.0.0

  1. Ready to work. Access gpfjs at {machine IP}:4200 from your browser.

Table of machines in the office and their IP addresses:

Machine

IP address

dory

10.0.1.1

nemo

10.0.1.2

pooh

10.0.1.6

piglet

10.0.1.7

kowalski

10.0.2.239

felix

10.0.2.251

shifu

10.0.2.252

simba

10.0.2.253

eyoree

10.0.2.237