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: developer-guide/20-User interface/01-introduction.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ Every Pioreactor, either worker or leader, have a web server on them. However, o
8
8
9
9
### Web server
10
10
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`.
12
12
13
13
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`.
14
14
@@ -17,15 +17,15 @@ The default protocol is `http` served on port `80`. To use `https` requires a ce
17
17
18
18
### Backend
19
19
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).
21
21
22
22
:::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.
24
24
:::
25
25
26
26
### Frontend
27
27
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.
29
29
30
30
31
31
### DNS name resolution to `pioreactor.local`
@@ -35,12 +35,12 @@ To allow for `pioreactor.local` to be an alias for `<leader hostname>.local`, we
35
35
36
36
### Updating and restarting the web UI
37
37
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.
0 commit comments