You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+71-30
Original file line number
Diff line number
Diff line change
@@ -18,50 +18,91 @@ The easiest way to have a look at some graph visualizations is to check out the
18
18
19
19
If you are using vg and want visualize the graphs it generates, the online version is limited to small file sizes. For visualizing bigger data sets you can run the Sequence Tube Map on your own. You can either run the Tube Map completely on your local machine or use your local browser to access a Tube Map server running on any other machine you have access to.
20
20
21
-
### Prerequisites
21
+
### Install Prerequisites
22
22
23
-
* The NodeJS version [specified in the `.nvmrc` file](https://github.com/vgteam/sequenceTubeMap/blob/master/.nvmrc), which as of this writing is **18.7.0**. Other several other NodeJS versions will work, or at least mostly work, but only this version is tested. This version of NodeJS can be installed on most systems with [nvm](https://github.com/nvm-sh/nvm).
23
+
The Sequence Tube Map needs NodeJS, NPM, and [vg](https://github.com/vgteam/vg).
24
+
25
+
1. The simplest
26
+
27
+
28
+
29
+
* The NodeJS version [specified in the `.nvmrc` file](https://github.com/vgteam/sequenceTubeMap/blob/master/.nvmrc), which as of this writing is **18.7.0**. Several other NodeJS versions will work, or at least mostly work, but only this version is tested. This version of NodeJS can be installed on most systems with [nvm](https://github.com/nvm-sh/nvm).
24
30
* NPM. NPM comes included in most NodeJS installations. Ubuntu packages it as a separate `npm` package.
25
31
*[vg](https://github.com/vgteam/vg) (vg can be tricky to compile. If you run into problems, there are docker images for vg at [https://github.com/vgteam/vg_docker](https://github.com/vgteam/vg_docker).)
26
32
27
33
The directory containing the vg executable needs to be added to your environment path:
Alternately, you can close and re-opne your terminal, and navigate back to the `sequenceTubeMap` directory.
62
+
7. Install the version of NodeJS that the Sequence Tube Map [asks for in its `.nvmrc` file](https://github.com/vgteam/sequenceTubeMap/blob/master/.nvmrc). As of this writing that is **18.7.0**. You can install the right version automatically with `nvm`:
63
+
```
64
+
nvm install
65
+
```
66
+
8. Activate the appropriate version of NodeJS:
67
+
```
68
+
nvm use
69
+
```
70
+
9. Install the excact versions of NPM dependencies thast the Sequence Tube Map is tested against:
71
+
```
72
+
npm ci
73
+
```
74
+
Note that this is using **npm**, not **nvm** as in the previous step.
75
+
10. Build the frontend:
76
+
```
77
+
npm run build
78
+
```
51
79
52
80
### Execution
53
81
54
-
- Start the node server:
55
-
```
56
-
npm run serve
57
-
```
58
-
- If the node server is running on your local machine, open a browser tab and go to `localhost:3001`.
59
-
- If the node server is running on a different machine, open a local browser tab and go to the server's URL on port 3001 `http://<your server's IP or URL>:3001/`.
60
-
If you cannot access the server's port 3001 from the browser, instead of configuring firewall rules etc., it's probably easiest to set up an SSH tunnel.
1. Open your terminal. On Mac, hit `Command` + `Space`, type `terminal.app`, and hit `Enter`. On Linux, you can usually hit `Ctrl` + `Alt` + `T`.
85
+
2. Switch to the `sequenceTubeMap` directory:
86
+
```
87
+
cd sequenceTubeMap
88
+
```
89
+
If you didn't clone the Git repository immediately inside your home directory, you may need to navigate to another directory first.
90
+
3. Activate the appropriate version of NodeJS. If you installed `nvm` to manage NodeJS versions, you can run:
91
+
```
92
+
nvm use
93
+
```
94
+
4. Start the Sequence Tube Map server:
95
+
```
96
+
npm run serve
97
+
```
98
+
Note that this is using **npm**, not **nvm** as in the previous step.
99
+
5. Open the Sequence Tube Map in your browser.
100
+
- If you are running the Sequence Tube Map on your local computer, you can visit [http://[::]:3001](http://[::]:3001) or [http://localhost:3001](http://localhost:3001).
101
+
- If you are running the Sequence Tube Map on a *different* computer (for example, one accessed by SSH), you will need to connect to it there. You can try browsing to port 3001 on that machine's hostname. For example, if you connected with `ssh [email protected]`, then `bigserver.example.edu` is the hostname, and you want to visit `http://bigserver.example.edu:3001`. If that doesn't work, you can try setting up an SSH tunnel by making a second SSH connection with:
0 commit comments