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
+4-44Lines changed: 4 additions & 44 deletions
Original file line number
Diff line number
Diff line change
@@ -10,27 +10,14 @@ To install this service, the fist time, you will need to:
10
10
11
11
1. Required tools and versions:
12
12
1. Install `node` and `npm` according to the directions at https://nodejs.org/en/download/package-manager
13
+
2.`make` and `docker` are used for local development
13
14
2. Clone the service: `https://github.com/Local-Connectivity-Lab/ccn-coverage-vis`
14
15
3. Configure:
15
16
1.`cd cd ccn-coverage-vis`
16
17
1. Edit `src/utils/config.ts` and set the correct URL for your API host (if you're testing or you're deploying to a new URL).
17
18
18
-
19
-
## Deploying
20
-
Once the service has been setup (as above), it can be deployed using the following process:
21
-
1. Login to the coverage-host
22
-
2. Pull the lastest version from github
23
-
3. Restart the service
24
-
25
-
The shell commands are:
26
-
```
27
-
ssh coverage-host
28
-
cd ccn-coverage-vis
29
-
git pull
30
-
npm install
31
-
npm run build
32
-
pm2 restart Vis Server
33
-
```
19
+
## Development
20
+
Avoid committing your change directly to the `main` branch. Check out your own private branch for your development and submit a pull request when the feature/bug fix/cleanup is ready for review. Follow the [Angular Commit Message Conventions](https://github.com/angular/angular/blob/main/contributing-docs/commit-message-guidelines.md) for your commit message. Versions will be managed based on those commit messages.
34
21
35
22
## Troubleshooting & Recovery
36
23
When a problem occurs, there are several checks to determine where the failure is:
@@ -56,22 +43,6 @@ Look in the first column, Status:
56
43
* Timeout or unreachable error: Something is broken in the network between your web browser and the coverage-vis host.
57
44
58
45
59
-
### Checking ccn-coverage-vis with pm2
60
-
Next, confirm ccn-coverage-vis is operating as expected. To do this, you will need to be able to log into the server hosting the coverage service.
61
-
62
-
Use `pm2 list` to confirm the "Vis Server" is **online**
63
-
```
64
-
ssh coverage-host
65
-
pm2 list
66
-
```
67
-

68
-
69
-
If the "Vis Server" is not online as expected, restart it with:
70
-
```
71
-
pm2 restart Vis Server
72
-
```
73
-
74
-
75
46
### Checking nginx
76
47
If there appear problems with nginx, then check that the
77
48
@@ -100,18 +71,7 @@ If nothing else works, the last option is a clean reinstall of the service. The
100
71
101
72
## Testing
102
73
103
-
Changes to the main branch are automically built and deployed to: https://seattlecommunitynetwork.org/ccn-coverage-vis/
104
-
105
-
Once changes have been validated, they can be deployed with:
106
-
107
-
```
108
-
ssh coverage-api.westus2.cloudapp.azure.com
109
-
cd ccn-coverage-vis/
110
-
git switch main
111
-
git stash
112
-
git pull
113
-
npm install
114
-
```
74
+
We provide a docker compose environment for local testing. Run `docker compose up -d`, and the web server will be running on your local host at port `443`.
0 commit comments