shawn/op-pedal
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #480 from FoolHen/docs_fixes

Browse Source 
Fix some docs issues
This commit is contained in:
Robin Davies
2026-05-23 01:06:06 -04:00
committed by GitHub
parent feb1c2fef1 ca51358028
commit 4b5244f68e
2 changed files with 4 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/BuildPrerequisites.md
+1 -2
View File
@@ -10,7 +10,6 @@ Run the following commands to install build tools required by the PiPedal build.
The PiPedal build process also requires version 12 or later of `node.js`. Type `node --version` to see if you have a version
of `node.js` installed already. Otherwise run the following commands as root to install a current version of version of `node.js`:
sudo apt install nodejs npm curl
@@ -27,7 +26,7 @@ Run the following commands to install dependent libraries required by the PiPeda
authbind libavahi-client-dev libnm-dev libicu-dev \
libsdbus-c++-dev libzip-dev google-perftools \
libgoogle-perftools-dev \
libpipewire-0.3-dev libbz2-dev
libpipewire-0.3-dev libbz2-dev librsvg2-dev
### Installing Sources
docs/Debugging.md
+2 -2
View File
@@ -29,7 +29,7 @@ You must stop the pipedald service before launching a debug instance of pipedald
or
pipedalconfig -stop #Stops the Jack service as well.
pipedalconfig --stop #Stops the Jack service as well.
Although not strictly necessary, you should probably add your login account to the pipedal_d group.
@@ -38,7 +38,7 @@ Although not strictly necessary, you should probably add your login account to t
This will allow you to run `pipedald` under the debugger of your choice using the
same /etc/pipedal and /var/pipedal directories as an instance of `pipedal` running
under systemd. Note that when running under systemd, `pipedald` runs under an unprivileged
`pipedal_d` service account, and relies it's group (also 'pipedal_d`) in order to access its
`pipedal_d` service account, and relies it's group (also `pipedal_d`) in order to access its
data files, and to communicate with the `pipedaladmin` service, which does run with root
privileges when `pipedald` needs to perform operations that do required root privileges (e.g. shutdown/reboot and starting and stopping WiFi services).