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
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,16 +15,20 @@ The frontend was built using:
15
15
16
16
Github Actions will test, build and upload the frontend to the [labctl repo](https://github.com/labctl/labctl/tree/main/helpers/frontend/html).
17
17
18
-
#Local testing
18
+
## Testing the frontend locally
19
19
20
-
For local testing you could point it towards another running labctl server instance. This instance is define in the **localhost** variable in Local Storage. You can change this in Web Tools: Application->Local Storage from the default, *tes4:8080*.
20
+
When the frontend opens it usually connects to the host and URL on which it was served,- this will not work while testing the frontend on localhost with vite.
21
21
22
-
When the frontend opens on a http://localhost:* URL it will use the **localhost** variable, else it will connect to the host and URL on which it was served.
22
+
For local testing you should point the fontend toward a running labctl server instance. This instance is defined in the **localhost** variable in Local Storage. You can change this in Web Tools: Application->Local Storage from the default, `https://tes4:8080/labctl`.
23
23
24
24
1. Clone the repo and install deps: `npm install`
25
25
2. Start the web server with `npm run dev` or `npx vite`
26
-
3. When the frontend runs on http://localhost it will try to connect to a server identified by the value of **localhost** in Local Storage
26
+
3. When the frontend runs on <http://localhost> it will try to connect to a server identified by the value of **localhost** in Local Storage
27
27
28
-
# Local unit tests
28
+
##Local unit tests
29
29
30
30
`npm test` or `npx vitest` for continuous testing during development
31
+
32
+
## Web API endpoints & Websocket messages
33
+
34
+
These are documented in the labctl main repo's README file - [labctl/labctl](https://github.com/labctl/labctl)
0 commit comments