Skip to content

Commit 6e662e9

Browse files
updateS
1 parent 222c7cf commit 6e662e9

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

developer-guide/20-User interface/01-introduction.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Every Pioreactor, either worker or leader, have a web server on them. However, o
88

99
### Web server
1010

11-
The web server we use is lighttpd, and hosted from `/var/www/pioreactorui`. This folder is actually a git repo, and pulls from [pioreactorui](https://github.com/pioreactor/pioreactorui) GH repo. Systemd controls starting and restarting lighttpd.
11+
The web server we use is lighttpd, and loaded from `/opt/pioreactor/venv/bin/pioreactor-fcgi`.
1212

1313
The lighttpd conf file is located in `/etc/lighttpd/conf-enabled/50-pioreactorui.conf`. Error logs (though not helpful) are in `/var/log/lighttpd/error.log`.
1414

@@ -17,15 +17,15 @@ The default protocol is `http` served on port `80`. To use `https` requires a ce
1717

1818
### Backend
1919

20-
The backend app is a Flask app, with entry point in `/var/www/pioreactorui/main.fcgi`. The app uses Huey as background workers to perform `pio` tasks, save to disk, etc. Huey is controlled by systemd `huey.service`. The API is [available here](/developer-guide/web-ui-api)
20+
The backend app is a Flask app, with entry point in `/opt/pioreactor/venv/bin/pioreactor-fcgi`. The app uses Huey as background workers to perform `pio` tasks, save to disk, etc. Huey is controlled by systemd `huey.service`. The APIs are [here](/developer-guide/api-reference) and [here](/developer-guide/unit-api-reference).
2121

2222
:::info
23-
Both workers and leaders have this backend. However, workers only use expose the `/unit_api/` endpoints. See full list [here](/developer-guide/web-ui-api).
23+
Both workers and leaders have this backend. However, workers only use expose the `/unit_api/` endpoints.
2424
:::
2525

2626
### Frontend
2727

28-
The frontend is a React app, built with Material UI. The source code is at [pioreactorui_frontend](https://github.com/Pioreactor/pioreactorui_frontend). A lot of the "data" for the frontend comes from YAML files on the RPi's filesystem. For example, all the charts, activities, and automations are defined in their own YAML file in a `contrib` folder on the filesystem. This way, it's easy to add new data to the frontend without having to write new JS.
28+
The frontend is a React app, built with Material UI. The source code is at [pioreactorui_frontend](https://github.com/Pioreactor/pioreactor/tree/master/frontend). A lot of the "data" for the frontend comes from YAML files on the RPi's filesystem. For example, all the charts, activities, and automations are defined in their own YAML file in a `~/.pioreactor/` folder on the filesystem. This way, it's easy to add new data to the frontend without having to write new JS.
2929

3030

3131
### DNS name resolution to `pioreactor.local`
@@ -35,12 +35,12 @@ To allow for `pioreactor.local` to be an alias for `<leader hostname>.local`, we
3535

3636
### Updating and restarting the web UI
3737

38-
To update on the UI on Pioreactor leader, use `pio update ui`. This also restarts the server.
38+
To update on the UI on Pioreactor leader, use `pio update app`. This also restarts the server.
3939

4040
To restart:
4141

4242
```
43-
sudo systemctl restart lighttpd && sudo systemctl restart huey
43+
sudo systemctl restart pioreactor-web.target
4444
```
4545

4646
### Logs

0 commit comments

Comments
 (0)