SLQ Wiki facilities:fablab:equipment-custom

CAD Box

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Jul 2018 14:27:15 +0000

CAD Box

These computer's are built using ICT upcycled disposed PCs.

Carboard Jigs

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Jul 2018 14:27:15 +0000

Carboard Jigs

Jigs for cutting down large cardboard sheets to size for the laser-cutter.

7000mm 400mm

This zip includes Fusion360, DXF and Enrroute file. The simple outline is probably the best to use.

700x400_jig_v2.zip

A2, A3, PET and Rayjet 300

Jigs for cutting material

jigs_a2_a3_pet_rayjet.dxf

Digital Signage Player

anonymous@undisclosed.example.com (Anonymous) — Wed, 13 Mar 2019 11:58:43 +0000

Digital Signage Player

This is where we are documenting our long and evolving search for the perfect fabrication lab signage. The signage will/has been used for basic info, but ideally can be adapted for use with specific equipment, quickly edited in-house and easily updated.

A brief explanation of each of the solutions we have trial or research is given, then detailed instructions are provided where appropriate. Resources for the signage can also found here.

Prototype One - The Pi-looper

IMPLEMENTED - in occasional use for installations

The pi-looper prototype was explored in 2015-2016 as a solution for signature programming by Daniel. It has two versions, one that uses video on the SD card, a second that plays back of a USB. Other options include output of sound over HDMI or minijack.

The Signage was used in the fabrication Lab in 2015 before the refurbishment.

Credit goes to Steven Hickson for this work, This is the latest info.

http://stevenhickson.blogspot.com.au/2015/04/rpi-videolooper-not-booting-blinking.html

Source is here.

https://github.com/StevenHickson/RPiVideoLooper

Check out the pi-maker documentation to make your own pi looper.

PROS:

Existing solution
Documented
Works
Minimal hardware spec (pi2)

CONS:

Only video files.
Limited Customisation

Verdict

Useful for stand-alone player only. Not updated easily or web-based.

Prototype Two - The Chromecast

STALLED - with ICTS networking

This was seen as possibly the cheapest way to get a remote screen working. It has stalled due to network requirements which SLQ ICT is working on. It seems the chromecast requires multicast and TCP/UDP set-up outside the scope of usual SLQ wifi networks. This uses a webpage as source which is opened in a browser (chrome) and then 'cast' to the chromecast.

Pros

Cheap solution
reliable, available hardware
will play video
can be used for presentations

Cons

Networking set-up is not enterprise friendly (requires multicast and dns)
Each screen requires a browser on another device (or possibly tabs?)

Prototype Three - The Pi Kiosk + Reveal.js Signage Server

implimented - then discarded due to need for extra node service needed on server

Based on a running a simple web slide show as the signage, with a pi running a web browser in kiosk (full screen) mode.

PROS:

Existing solution
Documented
Works
Minimal hardware spec (pi2)
Web-based

CONS:

Complexity of client/server

Raspberry Pi Kiosk

This is a pi running in kiosk mode which boots to full screen browser (using lxde autostart) and goes to web address using a web browser call kweb

Info found here

https://www.raspberrypi.org/forums/viewtopic.php?f=66&t=40860

Manuals here

http://steinerdatenbank.de/software/kweb_manual.pdf

The browser has comprehensive keyboard shortcuts, designed to control the pi entirely through a browser.

Signage Server

Many options exist for web signage, from simple stand-alone players to networked client-server models. As we want a simple proof-of-concept, I've gone with a simple web-based slide presenter called reveal.js. There is an online editor for making slides here Reveal.js can run locally, over a network on a server, or multicast over web sockets. For this prototype it run an the programming server.

Reveal.js

This was the first attempt. For our purposes I've hacked the index.html, modifying the css to fomat inline, a couple of pictures as background, added adding the supervisor's name (mick) and turned on autoslide in the js options.

This is the changed index.html, renamed to welcome.html

 <!doctype html>
<html>
	<head>
		<meta charset="utf-8">
		<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no">

		<title>welcome to The Fab Lab</title>

		<link rel="stylesheet" href="css/reveal.css">
		<link rel="stylesheet" href="css/theme/black.css">

		<!-- Theme used for syntax highlighting of code -->
		<link rel="stylesheet" href="lib/css/zenburn.css">

		<!-- Printing and PDF exports -->
		<script>
			var link = document.createElement( 'link' );
			link.rel = 'stylesheet';
			link.type = 'text/css';
			link.href = window.location.search.match( /print-pdf/gi ) ? 'css/print/pdf.css' : 'css/print/paper.css';
			document.getElementsByTagName( 'head' )[0].appendChild( link );
		</script>
	</head>
	<body>
		<div class="reveal">
			<div class="slides">
				<section data-background-image = "fabrication_lab_signage_v1-01.png">

        </section>
				<section data-background-image = "3pointcheck_one_page.png">
        <h1 style="color:black;align-content: center;margin-top: 580px;">
          Mick


          </h1>

        </section>
			</div>
		</div>

		<script src="lib/js/head.min.js"></script>
		<script src="js/reveal.js"></script>

		<script>
			// More info https://github.com/hakimel/reveal.js#configuration
			Reveal.initialize({
				history: true,

				// More info https://github.com/hakimel/reveal.js#dependencies
				dependencies: [
					{ src: 'plugin/markdown/marked.js' },
					{ src: 'plugin/markdown/markdown.js' },
					{ src: 'plugin/notes/notes.js', async: true },
					{ src: 'plugin/highlight/highlight.js', async: true, callback: function() { hljs.initHighlightingOnLoad(); } }
				]
			});
		</script>
	</body>
</html>

These are the background images:

and the settings changed in reveal.js are;


	// Loop the presentation
	loop: true,

         // Number of milliseconds between automatically proceeding to the
	// next slide, disabled when set to 0, this value can be overwritten
	// by using a data-autoslide attribute on your slides
	autoSlide: 7000,

	// Stop auto-sliding after user input
	autoSlideStoppable: true,

This is the working version revealjsfablab which can be copied to a server or opened locally.

~~You can see it running here: http://192.168.36.78/reveal/welcome.html#/~~

Prototype Four - The Pi Kiosk + Dokuwiki Reveal.js Signage Server

implimented - but broken - power pulled and wiped SD card

Reveal.js is great - but ideally we'd like to hang it off our wiki - Once again a dokuwiki plug-in to the rescue. Therevealjs plugin for dokuwiki lets us use standard wiki pages and markup to create our slides. Here us the welcome signage. For more examples check out the fabrication lab Fabrication Lab Signage page.

PI

Raspian Lite install built with pibakery, a gui based piSD authoring utility

Minimal customisation;

/LXDE-pi/autostart launches start.sh
start.sh has 180 sec delay then launches chromium, kiosk mode, pointed to signage http address
sudo crontab -e has shutdown at 830pm

Teensy

Arduino sketch that reads the teensy buttons and sends out up/down/left/right/F5/esc

/* Buttons to USB Keyboard Example

   You must select Keyboard from the "Tools > USB Type" menu

   This example code is in the public domain.
*/

#include <Bounce.h>

// Create Bounce objects for each button.  The Bounce object
// automatically deals with contact chatter or "bounce", and
// it makes detecting changes very simple.
Bounce button0 = Bounce(0, 10);
Bounce button1 = Bounce(1, 10);  // 10 = 10 ms debounce time
Bounce button2 = Bounce(2, 10);  // which is appropriate for
Bounce button3 = Bounce(3, 10);  // most mechanical pushbuttons
Bounce button4 = Bounce(4, 10);
Bounce button5 = Bounce(5, 10);  // if a button is too "sensitive"
Bounce button6 = Bounce(6, 10);  // to rapid touch, you can
Bounce button7 = Bounce(7, 10);  // increase this time.
Bounce button8 = Bounce(8, 10);
Bounce button9 = Bounce(9, 10);

void setup() {
  // Configure the pins for input mode with pullup resistors.
  // The pushbuttons connect from each pin to ground.  When
  // the button is pressed, the pin reads LOW because the button
  // shorts it to ground.  When released, the pin reads HIGH
  // because the pullup resistor connects to +5 volts inside
  // the chip.  LOW for "on", and HIGH for "off" may seem
  // backwards, but using the on-chip pullup resistors is very
  // convenient.  The scheme is called "active low", and it's
  // very commonly used in electronics... so much that the chip
  // has built-in pullup resistors!
  pinMode(0, INPUT_PULLUP);
  pinMode(1, INPUT_PULLUP);
  pinMode(2, INPUT_PULLUP);
  pinMode(3, INPUT_PULLUP);
  pinMode(4, INPUT_PULLUP);
  pinMode(5, INPUT_PULLUP);
  pinMode(6, INPUT_PULLUP);  // Teensy++ LED, may need 1k resistor pullup
  pinMode(7, INPUT_PULLUP);
  pinMode(8, INPUT_PULLUP);
  pinMode(9, INPUT_PULLUP);
}

void loop() {
  // Update all the buttons.  There should not be any long
  // delays in loop(), so this runs repetitively at a rate
  // faster than the buttons could be pressed and released.
  button0.update();
  button1.update();
  button2.update();
  button3.update();
  button4.update();
  button5.update();
  button6.update();
  button7.update();
  button8.update();
  button9.update();

  // Check each button for "falling" edge.
  // Type a message on the Keyboard when each button presses
  // Update the Joystick buttons only upon changes.
  // falling = high (not pressed - voltage from pullup resistor)
  //           to low (pressed - button connects pin to ground)
  if (button0.fallingEdge()) {
    Keyboard.press(KEY_LEFT);
  }
  if (button1.fallingEdge()) {
    Keyboard.press(KEY_RIGHT);
  }
  if (button2.fallingEdge()) {
    Keyboard.press(KEY_UP);
  }
  if (button3.fallingEdge()) {
    Keyboard.press(KEY_DOWN);
  }
  if (button4.fallingEdge()) {
    Keyboard.press(KEY_F5);
  }
  if (button5.fallingEdge()) {
    Keyboard.press(KEY_ESC);
  }
  if (button6.fallingEdge()) {
    Keyboard.println("B6 press");
  }
  if (button7.fallingEdge()) {
    Keyboard.println("B7 press");
  }
  if (button8.fallingEdge()) {
    Keyboard.println("B8 press");
  }
  if (button9.fallingEdge()) {
    Keyboard.println("B9 press");
  }

  // Check each button for "rising" edge
  // Type a message on the Keyboard when each button releases.
  // For many types of projects, you only care when the button
  // is pressed and the release isn't needed.
  // rising = low (pressed - button connects pin to ground)
  //          to high (not pressed - voltage from pullup resistor)
  if (button0.risingEdge()) {
    Keyboard.release(KEY_LEFT);
  }
  if (button1.risingEdge()) {
    Keyboard.release(KEY_RIGHT);
  }
  if (button2.risingEdge()) {
    Keyboard.release(KEY_UP);
  }
  if (button3.risingEdge()) {
    Keyboard.release(KEY_DOWN);
  }
  if (button4.risingEdge()) {
    Keyboard.release(KEY_F5);
  }
  if (button5.risingEdge()) {
    Keyboard.println("B5 release");
  }
  if (button6.risingEdge()) {
    Keyboard.println("B6 release");
  }
  if (button7.risingEdge()) {
    Keyboard.println("B7 release");
  }
  if (button8.risingEdge()) {
    Keyboard.println("B8 release");
  }
  if (button9.risingEdge()) {
    Keyboard.println("B9 release");
  }
}

Prototype Five - The picade + Dokuwiki + Reveals

Build on the suceess of the last version - its time make it all self contained and build in the essential features.

PROS:

Builds Existing solution
Minimal hardware spec (pi + picade hat)
Web-based

CONS:

Requires custom Pi Image
Requires Picade Hat ( for shutdown switch and extra buttons)

Install Retro Pi

Use official instructions

https://github.com/RetroPie/RetroPie-Setup/wiki/First-Installation

Install Picade hat

Once again, the official installer

https://github.com/pimoroni/picade-hat

Install Extras

xdtools to create a refresh loop (make the web browser refresh by pressing ctrl+f5 with a script)
unclutter to hide pointer

Configure Retro Pi

These instructions are based on this raspberry pi forum thread, summarised here.

Run Retro-pi Setup to boot to terminal - this is included in RetroPi and accessible on boot.

mod .bashrc to start start on TTY1 (this means the pi starts with the first virtual terminal - which we will then use to launch our desktop, otherwise for some reason it starts the desktop on a different terminal - meaning we can't see it…)

# Startx if [[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]]; then exec startx; fi

Edit the default user (called pi) autostart, which sets up our desktop, makes the mouse disappear after 5secs with unclutter, and calls a couple of scripts which we will write next.

nano /home/pi/.config/lxsession/LXDE-pi/autostart

@lxpanel --profile LXDE-pi
@pcmanfm --desktop --profile LXDE-pi
@point-rpi
@xset s off
@xset s noblank
@xset -dpms
@unclutter -idle 5 -root
@/home/pi/start_URLrefresh.sh
@/home/pi/start_chromium.sh

Create Start-up Scripts

nano /home/pi/start_chromium.sh

# Run browser after boot to desktop
/bin/sleep 3
# run as pi user
sudo -u pi 
# clean chromium on disk prefs to disable messages
sed -i 's/"exited_cleanly":false/"exited_cleanly":true/' ~/.config/chromium/'Local State'
sed -i 's/"exited_cleanly":false/"exited_cleanly":true/; s/"exit_type":"[^"]\+"/"exit_type":"Normal"/' ~/.config/chromium/Default/Preferences
# launch  chromium
chromium-browser --kiosk --no-default-browser-check --no-first-run --disable-infobars --disable-session-crashed-bubble 
# End of script

nano /home/pi/start_URLrefresh.sh

# Start a goofy command loop to refresh the browser every 560 seconds usubg xdt$
/bin/sleep 6
/usr/bin/lxterminal --command watch -n 560 xdotool key ctrl+F5 &
# End of goofy script

Configure Chromium

All we need to to is set our desired slide as the homepage, this way when Chromium launches, it goes straight to the slide we want. For example, to set the player to display the welcome signage for the Fabrication Lab - the link below will work.

http://wiki.edgeqld.org.au/doku.php?do=export_revealjs&id=facilities:fablab:signage:welcomepi-signage&theme=welcome#/

Just set the link as the homepage in chromium.

Its important to use an external link and not a wiki link.

Future Changes

Things that could be built into future versions.

What if Wifi goes Down?

And it always does… check out this

http://weworkweplay.com/play/rebooting-the-raspberry-pi-when-it-loses-wireless-connection-wifi/External Link

Chron Shutdown timer

Digital Signage Resources

laser_cutter_monitor_signs_preflight_v2.ai

3pointcheck.pdf

3d_printer_monitor_signs.pdf

fabrication_lab_signage_v1.ai

3pointcheck.jpg

fabrication_lab_signage_v1-01.svg

fabrication_lab_signage_v1-02.svg

fabrication_lab_signage_v1-03.svg

fabrication_lab_signage_v1.svg

Fablab FOGBERRY Server

anonymous@undisclosed.example.com (Anonymous) — Thu, 12 Aug 2021 12:19:30 +0000

Fablab FOGBERRY Server

The FOG server is located in the basement next to the wiki server. FOG (Free and Open-source Ghost) is an imaging and deployment solution for linux/windows/mac. We use it to make images of the various PCs in use around the fablab, as well as storing any files needed for updates, re-installs, etc. In 2018 the server was updated to include Berryboot to image Raspberry Pis.

Rationale

The FOG server solves the problem of backing up and deploying The Edge computers that are not maintained by SLQ ICT. With you number of software packages and combinations of hardware in use in the basement, management became time consuming and inefficient. A solution was researched and trialled in 2013 for the CCC program and has been rolled over into general fabrication lab use.

FOG server Quick Start Guide

The main use of the FOG server is to re-image computers once updated or install an image on an new computer. Both these tasks can be accomplished by the same method, without needing to access the fog server itself. There is a small self-contained wired network attached to the server, that PCs can be plugged into and imaged from.

Deploy an Image

This is fancy talk for copying one of the saved computer images, stored on the fog server, to a new computer. This will generally only work if the image and the new computer have the same hardware. And is only legal if the license for the OS you are cloning permits it. The exception to this is linux images - you can make a basic (x)ubuntu image and expect to be able to clone it. Ask the Fabrication Lab supervisor about the current list of images.

Before you start deploying, here is a checklist to work through:

Check your firmware (BIOS or EFI):
- Your computer needs to be correct SATA mode (try IDE/legacy first - if this doesn't work try AHCI)
- Check PC hard-drive size
- Must be the same or larger than the image you want to deploy
- Network boot must be enabled

Plug it In

Connect your PC to power and the FOGBERRY network. Its important to power a laptop through the whole process.

Boot From Network

Turn on your PC and boot from the network card. On HP computers this is F12.

FOG MENU

Once at the fog menu, select “deploy image', then enter the username and password, and deploy your image.

Berryboot Server

Berryboot is a simple boot selection screen for ARM computers like the Raspberry Pi, that allows you to put multiple Linux distributions on a single SD card.In addition it allows you to put the operating system files on an external USB hard drive instead of on the SD card itself. ¹⁾

We are using berryboot deployed from our fablab fog-server as our final method of installing raspberry pi OSes - this section is based on the official berryboot documentation.

Install Berryboot

Download the latest berryboot. To install: extract the contents of the .zip file to a normal (FAT formatted) SD card, and put it in your Raspberry Pi. This can be simply done under Windows without any special image writer software. Once you start your Pi it will start an installer that reformats the SD card and downloads the operating systems files.

The server is accessible from the fog-server stand-alone network as:

cifs://10.0.0.253/berryboot

Making a Berryboot Image

To make a new custom image we use a linux(Xubuntu) system with kpartx installed. You can do this from the documentation station, or any floating laptop.

$ sudo kpartx -av image_you_want_to_convert.img 
add map loop0p1 (252:5): 0 117187 linear /dev/loop0 1
add map loop0p2 (252:6): 0 3493888 linear /dev/loop0 118784
$ sudo mount /dev/mapper/loop0p2 /mnt
$ sudo sed -i 's/^\/dev\/mmcblk/#\0/g' /mnt/etc/fstab
$ sudo mksquashfs /mnt converted_image_for_berryboot.img -comp lzo -e lib/modules
$ sudo umount /mnt
$ sudo kpartx -d image_you_want_to_convert.img

¹⁾

https://www.berryterminal.com/doku.php/berryboot

FabLab Server

anonymous@undisclosed.example.com (Anonymous) — Fri, 23 Oct 2020 09:23:00 +0000

This is an archived page , no further development is anticipated

FabLab Server

The fablab server is an in-house edge programming server, running the internal wiki. The need for a hosted wiki has come about through the mortal need for documentation, inspired in part by the CCC project. Researching the available wiki software (including confluence available on SLQ networks) we settled Dokuwiki. Dokuwiki is simple to edit, maintain and back-up. It doesn't require a database for installation and can be edited from any modern web browser. The wiki uses a custom template and has a few extensions installed.

The Fablab Server is used for development over the internal networks only!! It is not secured enough for external deployment, the instructions here are considered solely for an internal, private server.

Hardware

The server runs on a recycled HP8100 mid-tower. Its physically located in The Edge's Fabrication Lab.

Software

~~The server is running Ubuntu 15.10, with a LAMP stack.~~Ugraded to 16.04.

rdiff backup with cron to external USB drive

The back-up routine is daily to an external drive. This will be augmented to a second drive and hopefully some space on an ICTS asset somewhere…

The server runs a cron job (a regular scheduled task) to back up the entire web directory (www) to an external drive.

Finding and Mounting drives and directories

First lets check the www directory - normally it resides in /var/www/html

ls -al /www/www

UIn our case, these are symlinked to another location²⁾. For example the dokuwiki install is:

lrwxrwxrwx 1 www-data www-data 17 Mar 17  2016 /var/www/html/dokuwiki -> /www/www/dokuwiki

The /www folder is actually another drive mounted on boot - check it with nano /etc/fstab

# /www was on /dev/sdb1 during installation
UUID=d497c901-515c-456f-bddd-aaa5684c4bd3 /www            ext4    defaults        0       2

Now lets mount our backup USB on boot - First chuck it in then find the UUID using sudo blkid

/dev/sdc1: LABEL="edgeserverbkup" UUID="620df2f1-4787-4584-93d3-2cb4ad24d983" TYPE="ext4" PARTUUID="ad59a428-01"

Then edit fstab to mount on boot.

UUID=620df2f1-4787-4584-93d3-2cb4ad24d983 /mnt/externalusb        ext4    defaults        0       1

Now its time to reboot.

Using rdiff-backup

From rdiff-backup;

rdiff-backup backs up one directory to another, possibly over a network. The target directory ends up a copy of the source directory, but extra reverse diffs are stored in a special subdirectory of that target directory, so you can still recover files lost some time ago. The idea is to combine the best features of a mirror and an incremental backup. rdiff-backup also preserves subdirectories, hard links, dev files, permissions, uid/gid ownership, modification times, extended attributes, acls, and resource forks. Also, rdiff-backup can operate in a bandwidth efficient manner over a pipe, like rsync. Thus you can use rdiff-backup and ssh to securely back a hard drive up to a remote location, and only the differences will be transmitted. Finally, rdiff-backup is easy to use and settings have sensical defaults.

What we want is a incremental back-up of the entire /www/www/ directory to /mnt/externalusb/www. With rdiff-backup this simple. First lets make our directory on our external drive.

sudo mkdir /mnt/externalusb/www

This is the command we want to run:

 rdiff-backup --preserve-numerical-ids /www/www /mnt/externalusb/www

run it once (as sudo) to check its working.

Next step is to make this happen daily..

Set up a Crontab

Access the system crontab.

sudo crontab -e

We want daily backups so add this line

@daily rdiff-backup --preserve-numerical-ids                      /www/www      /mnt/externalusb/www

Save and exit.

Automount USB

https://askubuntu.com/a/772387

Mobile Uploads

Why it was done

Motivated by the finicky nature of uploading I've hacked a together a solution that copies over uploaded photos to this namespace. The old method was:

take photo
upload over usb to computer
log into wiki
upload to wiki
go to media manager and insert photo.

New method is;

take photo on mobile (with this camera app - upupu on iOS)
or DAVsync on Android.
uploaded via webdav (this is built into upupu and occurs automagically with DAVsync)
go to media manager and insert photo.

Setup For Staff

iOS

IF you want to use your own IOS device - device install upupu app from store.

Set up the webdav settings in upupu with:

Webdav ON

server http://192.168.36.78/webdav/mobileupload/yourname

user : yourname

pass : yourpass

Source can be found on github

Android

Install DavSync from Google play or compile it yourself. Then, chose “DavSync” in your application drawer. Set up the following fields:

server http://192.168.36.78/webdav/mobileupload/yourname/

user : yourname

pass : yourpass

Source can be found on github.

Server Set-Up

The server has folder, accessable over webdav ( a simple file sharing system that is accessible over http), that is monitored by lsyncd. Lsyncd has a configuration file (written in lua) that tells its to copy the contents of the webdav folder into the media directory in the wiki.

Set-up webdav

Originally webdav was set-up with digest authorisation however a couple of the syncing apps would only use password, so we've switched to basic auth.

This is another reason the server is not production ready - basic auth should be over SSL only!!!

Apache Setup

First up webdav needs to be turned on in our apache2 server using

 sudo a2enmod dav
 sudo a2enmod dav_fs

Next we make a webdav directory on our data drive:

 sudo mkdir /www/www/webdav

And link to to our web directory

 sudo ln -s /www/www/webdav/ /var/www/html/webdav

Lets make a directory for mobile uploads.

 sudo mkdir /var/www/html/webdav/mobileupload

Now make directories in the webdav directory for each staff member

  sudo mkdir /var/www/html/webdav/mobileupload/phil

Change ownership so the apache2 server can read the link and directories;

 sudo chown -R www-data:www-data /var/www/html/webdav

Now edit the apache2 server sites-available with

 sudo nano /etc/apache2/sites-available/000-default.conf

And enter the following:

 
    Alias /webdav /var/www/html/webdav
  
      <Directory /var/www/html/webdav>
          DAV On
      AuthType Basic
      AuthName "webdav"
      AuthUserFile /var/www/passwd.dav
      Require valid-user
      </Directory>

Webdav Passwords

Now we need to add webdav users and create the passwords. For the first user use:

 sudo htpasswd -c /var/www/passwd.dav phil

You will be prompted to create a password for this user.

Then for following users try this:

 sudo htpasswd  /var/www/passwd.dav mick

Repeat for remaining users.

Next make sure your passwd.dav file is owned by the apache server.

 sudo chown www-data:www-data /var/www/passwd.dav

Lsyncd

Next install lsyncd with

sudo apt install lsyncd

Create a log directory

sudo mkdir /var/log/lsyncd
touch /var/log/lsyncd/lsyncd.{log,status}

Then create a cofiguration file directory.

sudo mkdir /etc/lsyncd

sudo nano /etc/lsyncd/lsyncd.conf.lua

And enter this lua code


settings ={
        logfile = "/var/log/lsyncd/lsyncd.log",
        statusFile = "/var/log/lsyncd/lsyncd.status"
}

--
-- This syncs our webdav to dokuwiki for photo uploads.

sync  {
        default.rsync,
--      wait = 15,
        delete = false,
        source = "/www/www/webdav/mobileupload/",
        target = "/www/www/dokuwiki/data/media/mobileupload/",
        rsync={
        owner = true,
        group = true,
        perms = true
        }
}

Now lets start lsyncd as a service

sudo service lsyncd start

This performs a basic rsync command whenever the “/www/www/webdav/mobileupload/” changes. We use the command delete = false to force lsyncd to leave new files in our destination directory untouched -why? See below…

Fixing Capitalisation issues

For some reason dokuwiki does not like CAPITALS in media filenames, neither in the name nor exstention. So while 2971057.jpg will appear in dokuwiki IMG_2971057.jpg or 2971057.JPG will not.

This is fine when using upupu, but both davsync (Android) and whatever Phil is using use capitalisation in the file names. As an added bonus Phil's app creates directories, which means we need to look through them recursivley.

To fix this there are a couple of scripts running in start up, triggered by a cronjob. Lets set them up now. First go super with

   sudo su

Next lets make a directory for our scripts

 mkdir -p /usr/scripts/photo_rename

The first scripts will set up some inotifywait watches on the mobileupload directories. I've used one per user so for Phil lets do:

 nano inotify_phil.sh

Then we set up a while loop that uses inotifywait to detect a file action, then triggers another script called exiftool_rename_phil.sh

   #!/bin/bash
   DIRTARGET=/var/www/html/dokuwiki/data/media/mobileupload/phil
   while true #run indefinitely
   do''
   inotifywait -r -e close_write  $DIRTARGET  &&  /bin/bash /usr/scripts/photo_rename/exiftool_rename_phil.sh
   done

Now lets make our script to rename the photo with the date and time using exiftool, then change the extension with mv

   
  #!/bin/bash
  DIRTARGET=/var/www/html/dokuwiki/data/media/mobileupload/phil
  exiftool '-FileName<CreateDate' -d %Y%m%d_%H%M%S%%-c.%%e $DIRTARGET/*.JPG  &&
  find $DIRTARGET -name *JPG -exec sh -c 'mv "$0" "${0%%.JPG}.jpg"; echo "Moved $0 to ${0%%.JPG}.jpg"' {} \;

Finally set-up a crontab to run the script on reboot. So 'crontab -e then add this line.

     @reboot /usr/scripts/photo_rename/inotify_phil.sh

Exporting Sections of the Wiki

When we need to take sections of the wiki offline to another location, follow this procedure;

Install New Wiki

Follow the steps here to make a new wiki.

Export Wiki Data

Now we

 sudo tar -pvczf dokuwiki.tar.gz  /www/www/dokuwiki  --exclude=/www/www/dokuwiki/data/page

Next lets grab only the one last apocalypse data.

sudo find /www/www/dokuwiki/ -type d  -name one_* | tar -pvczf dokuwiki_data.tar.gz  --include-from - 

tar -tf dokuwiki_data.tar.gz

Recovery Procedure

This document covers recovery of content from your wiki, fixing broken plugins or templates, and total back-up.

Content Recovery

The easiest way to recover content is using the built in old revisions editor accessible from the right menu.

Then your can view all the changes made to that page.

And choose two changes to view the differences. Either side by side;

Or inline.

If you want to revert changes, select the version of the page you want (click the blue link) and it will open the page with a note at the top..

Edit the page, once again you will see note at the top. IF this is correct, then just save the edit and the changes will be made, creating a new version of the page.

Fixing broken Plugins or Templates

If the formating or function of the wiki goes haywire because of template or plugin updates or changes, you can use the server back-up to restore previous versions. This is useful because most plugin and template makers don't keep old versions around, relying on the wiki user to keep backups of their own wikis.

Re-installing Plugins and Templates

Restoring old versions of Plugins or Templates

We use rdiff-backup to daily backup the wiki (and the entire www directory). To understand how the back-up works and set it up see here

Restoring a folder from rdiff-backup

Lets say the we need to restore a working version of the revealjs plugin, after foolishly upgrading it and breaking all our existing slideshows³⁾. We know that we want to go back to how the wiki was about 20 days ago, when the slideshow was still working.

First we need to know where the plugin is installed. Our wiki is located in

/www/www/dokuwiki

All dokuwiki plugs live in:

 dokuwiki/lib/plugins

They all have there own folder, so the full path to revealjs would be

/www/www/dokuwiki/lib/plugins/revealjs/

Now we know where we want our restored files to go to, lets see where rdiff-backup keeps our backups. The file structure is mostly preserved by rdiff-backup so our revealjs folder would be in on the back drive.

/mnt/externalusb/www/

inside the rdiff-backup-data/ directory

/mnt/externalusb/www/rdiff-backup-data/

Then we are after the incremental backups…(this will let us go back a certain time)

/mnt/externalusb/www/rdiff-backup-data/increments/

Finally we find the revealjs directory.

/mnt/externalusb/www/rdiff-backup-data/increments/dokuwiki/lib/plugins/revealjs/

The command we want is

rdiff-backup -r 20D

This will restore (-r) the file from 20 days ago.

So the full command to restore the revealjs directory contents from 20 days ago is..

rdiff-backup -r 20D  /mnt/externalusb/www/rdiff-backup-data/increments/dokuwiki/lib/plugins/revealjs/ /www/www/dokuwiki/lib/plugins/revealjs

Full Restore of the Wiki From USB drive

If disaster strikes and the wiki goes down but the server is fine, you can restore it all from the USB external backup. Because rdiff-backup makes a mirror (an exact copy) we can just use the built in usual linux copy command with the '-a' for archive flag.

sudo cp -a /mnt/externalusb/www/dokuwiki /www/www/dokuwiki

Full Restore of the Wiki and Server

If disaster double strikes, and the only thing left working is the USB external backup - then to recover the wiki will require a re-install of the server and dokuwiki. These instructions are adapted from ccclabs.edgqld.gov.au. They will require a computer on the The Edge basement SLQ network, with an ICT request to set a permanent DHCP lease for a MAC address.

Sort The Hardware

You will need an i5, with 4gig RAM and 100Gig HD. Just about any recent donation from ICTS will suite, but try to use one that is (a) not part of an existing workshop line (b) not radically overspec.

Install Server OS

I've adapted this from the official dokuwiki instructions. You will need internet access. We will install the desktop version of (X)ubuntu for ease of use.

First up, grab workshop USB stick and make a fresh install of Xubuntu 14.04 (follow the steps in CCC) then install using these instructions.

Get (or request) a fixed DHCP lease

If you are in an organisation that has an ICT department - get this underway early, as it can take a while. The purpose is to make the server available over a network with a fixed address.

You will need to give your ICT a port number where you are plugging the server in, and the MAC address of the network card in the new computer. The port number is where you want to physically plug the server in. The MAC address can be found with

ifconfig

Once you know these details, let your ICT department know.

Install Server Software

Now make sure you are up to date.

 sudo apt update && sudo apt upgrade

Dokuwiki need a web server and PHP. We use apache2 and PHP7.0.

  sudo apt install apache2 libapache2-mod-php7.0

Enable Apache Rewrite module. This lets us use pretty URLs

  sudo a2enmod rewrite

Apache Set-up

Next we need to set-up Apache,lets edit our default configuration.

  sudo nano /etc/apache2/sites-avialable/000*.conf

and change

  DocumentRoot /var/www/html

 DocumentRoot /var/www/dokuwiki

Next we need to deny access to directories we want to keep secure in the main apache.conf file.

sudo nano /etc/apache2/apache2.conf

For directory /var/www/ replace

      AllowOverride None

with

      AllowOverride All

Restart Apache2 service.

  sudo service apache2 restart

PHP Set-up

First lets install the GD library, which we need for using the PDF export.

sudo apt install php7.0-gd

Then lets add sqlite support for bits and pieces.

 
sudo apt install php7.0-sqlite3

We'll need to make a few modifications to our PHP settings to allow larger uploads and posts to our wiki.

 sudo nano /etc/php7.0/apache2/php.ini

Look for these two lines and change them to at least 15M (15 megabytes)

upload_max_filesize = 15M
post_max_size = 15M

Use CTRL+w to search in nano

We then need to make sure php has enough memory allocated to run the upload scripts.

memory_limit = 256M

Copy Wiki Content

Before we copy the wiki data back, lets install usbmount

sudo apt install usbmount

Mount the external USB backup

Once you've got the server up and running lets grab the USB backup - just plug it in and it should mount automagically - both on the desktop and under /home/yourusername/media

Finally - this is the same as above - just use the cp command to copy from the backup to the server.

 sudo cp -a /home/yourusername/media/externalusb/www/dokuwiki /www/www/dokuwiki

Change Template Paths

The final jiggery pokery is to set the template path for your new IP address. We need this as the theme we use is has some customisation. Go to the admin panel;

Then open Configuration

and scroll down to the Bootstrap3 Template config

Now change this IP

http://wiki.edgeqld.org.au/lib/tpl/bootstrap3/assets/bootstrap/edge/bootstrap.min.css

To your new IP discovered earlier.

²⁾

This is so we can do a systemback of the server, excluding the www data

³⁾

like I just did

Information Kiosk

anonymous@undisclosed.example.com (Anonymous) — Fri, 23 Oct 2020 09:22:09 +0000

This is an archived page , no further development is anticipated

Information Kiosk

Developed to fulfill in-house information presentation requirements for facilitated and stand alone use. Based on the signage player v5 with added optional functionality of an external bluetooth controller.

Components

Player

The player displays a web-slideshow which can be navigated using buttons. The player can be powered-off and reset.

Functions

controller

Display Content Management System (CMS)

Files

Case - Protoype front panel. panel.dxf

Lasercutter-PC

anonymous@undisclosed.example.com (Anonymous) — Fri, 23 Oct 2020 09:23:34 +0000

This is an archived page , no further development is anticipated

Lasercutter-PC

This PC is a standard up-cycle, on a HP8100 minitower, running windows 7 Pro. The latest image of this PC can be found on the fog-server.

Hardware

Software

This is a standard install, with the addition programs being Corel Draw.

Windows powershell has been upgraded to 4.0, and 'PSReadline' is installed to allow bashlike autocomplete.

Laser Lense Inspection Jig

anonymous@undisclosed.example.com (Anonymous) — Mon, 23 Jul 2018 14:27:15 +0000

Laser Lense Inspection Jig

An essential part of documenting the laser lens maintenance is inspecting and cleaning the lens. This page details the making of a jig to clean and check the laser lense for damage.

lensjigv1.zip

laser_lens_inspector_jig.cdr

Pi Maker

anonymous@undisclosed.example.com (Anonymous) — Fri, 23 Oct 2020 09:22:38 +0000

This is an archived page , no further development is anticipated

Pi Maker

This a guide for making Raspberry Pi OS systems using the Pi-Maker in the Fabrication Lab

Using the PiMaker

We cover making custom video looper images for video playback or simple digital signage. You can also make the standard pi images.

Video Player

The first step is to make an SD card that the pi can use as an Operating System. The pi uses the SD as its main file system, and we've got a couple of options here for video playback.

To do this we write a disk image to an SD card using a disk utility - remember - This wipes the SD card!!

(1) Insert your SD card and double click the shortcut ' pi maker' on the desktop

→ Read more...

Signage Player

See Video Format Guidlines for a spec sheet on file formats.

See make a pi case out of 3mm acrylic for instructions on cutting a case

Making a Pimaker

The pimaker is a re-purposed old desktop computer running Xubuntu 14.04. It is a customised install for making rasperry pi (or any other disk image) using a basic rough and ready script GUI.

Video Looper for RPi 3

So there were issues with the RPi 3 and the image we have on the pimaker box. I've had to build a new image and adjust some of the scripting to make it work. I also loaded the files onto the SD Card and eliminated the step with the USB Stick (as the USBs that QM have for QANZAC don't register on the RPis; weird.

I used Tim Swartz's RPi Video Looper Image which seems to work fine the the RPi 3. I made a change in the startvideo.sh (used nano startvideo.sh) modifying the omx setting listed in the (somewhere in the bottom third of the script) from -o hdmi to -o local, which switches the sound playback to the 3.5 jack.

#/usr/bin/omxplayer -r -o hdmi $FILES${vids[$current]} to
#/usr/bin/omxplayer -r -o local $FILES${vids[$current]}

After finalising this, ran the RPi Config and expanded out the file system to make use of the whole disk

sudo raspi-config (then follow the instructions).

From the terminal used the following command line to copy files;

cp /mnt/usbdisk/filename.mp4 /home/pi/video
sudo reboot

Pull the USB at end of shutdown and the RPi is good to go.

Projection Shell

anonymous@undisclosed.example.com (Anonymous) — Mon, 10 Aug 2020 15:52:44 +0000

Projection Shell

https://a360.co/2Mvg6Qq

Fabrication Lab Sign IN System

anonymous@undisclosed.example.com (Anonymous) — Fri, 23 Oct 2020 09:24:46 +0000

This is an archived page , no further development is anticipated

Fabrication Lab Sign IN System

IPAD System

Laptop System

As of 2017, we've moved to having two upcycled laptops available for login at all times. For more details on the basic set-up see here. The only addition to the basic set-up is a script that launches chrome called startup_chrome.command in the edgeuser home directory.

  /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --kiosk

RFID System

HtE has developed the sign-on system to the point where it is a self-contained system running on the a Raspberry pi. The pi reads the cards, checks against a local database and logs users in. Users can also manually log in.

We discussed his current implementation and the the security implications (late 2016), and came up with an approach that we think would meet the need for SLQ ICTS data security. HtE is confident that he can modify the existing software to break it into a client - server module.

Custom Equipment

anonymous@undisclosed.example.com (Anonymous) — Tue, 07 Jan 2020 09:47:43 +0000

Custom Equipment

This is where the custom builds we use at The Edge are documented. We will be moving trello board content here if appropriate and consolidating other scattered resources. These tools could be hardware,software based, or hybrid software/hardware systems. Topics covered include set-up guides, workflows, procedures, programs and presets.