Skip to main content

Setting-Up Files, Folders and Setting Permissions

Files & Folders

Create the recommended folder and file structure:

cd $HOME;
mkdir -p meetings/lib/ meetings/bin/ meetings/recordings/;
touch meetings/bin/meeting-start meetings/bin/meeting-stop meetings/bin/meeting-follow;
chmod 755 meetings/bin/meeting-start meetings/bin/meeting-stop meetings/bin/meeting-follow;
touch meetings/lib/paths.sh meetings/lib/whisper.sh;
Editing the Scripts

Enter the scripts' contents into the prepared files using your preferred editor. 

If you are not comfortable using a command line editor like vi, pico or nano, use any text or code editor on your main computer and copy the files by the way of scp or a (s)ftp client onto the Raspberry Pi 500.  

PermissionsChecking the Scripts Are Executable

CheckNow check the permissions. meeting-start, meeting-stop and meeting-follow have to be executable. (This is done by chmod 755 above.) 

ls -l meetings/bin/

You should see a result like this: 

mela@Cox:~ $ ls -l meetings/bin/
total 20
-rwxr-xr-x 1 mela mela  526 Jan 11 08:51 meeting-follow
-rwxr-xr-x 1 mela mela 4558 Feb 21 00:17 meeting-start
-rwxr-xr-x 1 mela mela 2596 Feb 21 00:24 meeting-stop

-rwxr-xr-x means the file is executable (for user, group and world). 

Adding the Scripts to the PATH environment variable

Add $HOME/meetings/bin/ to the command line's path. 

vi .bashrc

Add a last line: 

export PATH="$HOME/meetings/bin:$PATH"

Save, and close the editor. Then load the updated .bashrc into your active session by entering: 

source .bashrc

Back to top