Recipe for a Raspberry Pi Kiosk

8th September 2017 by Alan 10 Comments

Ingredients

Raspberry Pi 3 B wireless

<br>

16Gb micro sd card

HDMI Cable

USB power cable

Case

Temporary USB Keyboard & USB mouse

Preparation and Cooking time

About 1 to 2 hours depending how many mistakes you make and start again 🙂

Method

Preparation

Download Raspberian Stretch Lite from https://www.raspberrypi.org/downloads/raspbian/
Unzip on to your computer
Obtain Etcher to burn the image onto the SD card
detailed instructions https://www.raspberrypi.org/documentation/installation/installing-images/README.md

First Boot

Insert SD card to Raspberry. Plugin HDMI to Raspberry – TV / Monitor. Plugin in USB keyboard. Plugin the power, should boot to a login screen.

user: pi

password: raspberry

Basic Setup

Set up secure password (option 1) – as SSH opens up access

Set up host name ( option 2)- makes it easier to find for login in as SSH

Set up Boot Options (option 3 -> B1 – >B2 ) – we will want the Raspberry to Boot into Console / Autologin

Set up SSH (option 5 -> P2 ) – this is important – as once you set up a true kiosk you can’t login, so SSH gives you away to set up easily. (option 5 -> P2 )

This is all done by the Raspberry Configuration tool

sudo raspi-config

1	sudo raspi-config

Set up Wireless Access

If you are not using an ethernet cable you will need to set up Wireless access. Raspberry instructions here https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md

Edit the config file ( I will use vi but you can use nano ).

sudo vi /etc/wpa_supplicant/wpa_supplicant.conf

1	sudo vi /etc/wpa_supplicant/wpa_supplicant.conf

and add a network, you can generate this with

wpa_passphrase yourSSID  yourwirelesspassword

1	wpa_passphrase yourSSID yourwirelesspassword

which outputs

network={
ssid="yourSSID"
#psk=" yourwirelesspassword"
psk=fdcdd08a9d6bd739f544a902c1a59dd8a7eedea30b4e4ba1afa61d3cf01222df
}

network={

ssid="yourSSID"

#psk=" yourwirelesspassword"

psk=fdcdd08a9d6bd739f544a902c1a59dd8a7eedea30b4e4ba1afa61d3cf01222df

}

so you can if you want to be fast and if you like to append directly

sudo wpa_passphrase yourSSID  yourwirelesspassword >> /etc/wpa_supplicant/wpa_supplicant.conf

1	sudo wpa_passphrase yourSSID yourwirelesspassword >> /etc/wpa_supplicant/wpa_supplicant.conf

I found I had reboot to activate.

sudo reboot

1	sudo reboot

Test SSH

OK you should be all ready to test connecting from your computer on the same lan via SSH

linux or Max terminal

ssh your-pi-hostname -l pi
password:  yourpasswordyouset

1 2	ssh your-pi-hostname -l pi password: yourpasswordyouset

If you are on Windows, you will probably use Putty for SSH.

and you should be in!

Install all the software needed

sudo apt-get update

1	sudo apt-get update

to make sure all is updated ( and you are connected to the internet )

sudo apt-get install chromium-browser

1	sudo apt-get install chromium-browser

to get Chromium

you will also need xinit

sudo apt-get install xinit

1	sudo apt-get install xinit

and xdotool

apt-get install xdotool

1	apt-get install xdotool

Setting up the X window

Before going full kiosk lets see if Chromium will launch.

edit the .xinitrc file in pi home directory

vi ~pi/.xinitrc

1	vi ~pi/.xinitrc

and input

#!/bin/sh
WIDTH=`xwininfo -root|grep Width | awk '{ print $2}'`
HEIGHT=`xwininfo -root|grep Height | awk '{ print $2}'`

exec chromium-browser --window-size=$WIDTH,$HEIGHT

#!/bin/sh

WIDTH=`xwininfo -root|grep Width | awk '{ print $2}'`

HEIGHT=`xwininfo -root|grep Height | awk '{ print $2}'`

exec chromium-browser --window-size=$WIDTH,$HEIGHT

The width and height are there as I found Chrome doesn’t know how to go full size. You can apparently to it in chromium defaults file, but this way is easier.

Now login on the console (not via SSH) via the keyboard and mouse attached to the pi and type

startx

startx

Chromium should launch and you should be able to browse the web

Set up the Kiosk

we add

xset s off
xset s noblank
xset -dpms

xset s off

xset s noblank

xset -dpms

to turn off screen savers

We add an hourly loop ( if required, or adjust the time in seconds ) to refresh the page (ctrl-F5)

(
while true
do
sleep  3600
xdotool key "ctrl+F5"
done
) &

(

while true

sleep 3600

xdotool key "ctrl+F5"

done

) &

and some more options to chromium –

-incognito --kiosk http://your-site

1	-incognito --kiosk http://your-site

I also found I needed this --disable-webgl as one webpage page wasn’t displaying properly, so the final file is

#!/bin/sh
WIDTH=`xwininfo -root|grep Width | awk '{ print $2}'`
HEIGHT=`xwininfo -root|grep Height | awk '{ print $2}'`
xset s off
xset s noblank
xset -dpms
(
while true
do
sleep  3600
xdotool key "ctrl+F5"
done
) &
exec chromium-browser --window-size=$WIDTH,$HEIGHT --disable-webgl --incognito --kiosk http://your-site

#!/bin/sh

WIDTH=`xwininfo -root|grep Width | awk '{ print $2}'`

HEIGHT=`xwininfo -root|grep Height | awk '{ print $2}'`

xset s off

xset s noblank

xset -dpms

(

while true

sleep 3600

xdotool key "ctrl+F5"

done

) &

exec chromium-browser --window-size=$WIDTH,$HEIGHT --disable-webgl --incognito --kiosk http://your-site

Start it on login

And then we want to auto start on login, I found the easiest was was to use .profile ( rc.local seemed to load too early )

vi ~pi/.profile

1	vi ~pi/.profile

and add

if [ -z "$SSH_TTY" ]; then
    startx -- -nocursor
fi

if [ -z "$SSH_TTY" ]; then

startx -- -nocursor

The if statement just stops us trying and failing to launch when an SSH login

-- -nocursor removes the mouse cursor

Tidy up boot up messages

Finally, when the PI is connected to the usb port of the monitor it will boot on power up, but there re lots of boot messages. I manged to get rid of most of them by editing cmdline.txt

sudo vi /boot/cmdline.txt

1	sudo vi /boot/cmdline.txt

and adding this to the single line

loglevel=0 logo.nologo quiet

1	loglevel=0 logo.nologo quiet

and also changing console=tty1 to console=tty3

Back it up

Nothing worse than doing all the work and then some how your SD card get corrupted – Backup the SD card.

Backup instructions here https://www.raspberrypi.org/documentation/linux/filesystem/backup.md

for linux users, put the card in your machine, find out what device it is and

sudo dd bs=4M if=/dev/sdbx of=raspbian.img

1	sudo dd bs=4M if=/dev/sdbx of=raspbian.img

where /dev/sdbx is the actual device name of your card of course

Did I miss anything?

I wrote this after the fact, so I could remember what I did if and when I do it again. I may have missed something, or something may need a better explanation, please use the comments box to let me know.

WordPress Plugin install fails with Forbidden, you don’t have permission to wp-admin/update.php on your server

21st June 2017 by Alan Leave a Comment

This issue is fairly common on servers that are running Apache with mod_sec ( mod security ). Mod security is a complex system that looks at the sort of web traffic ‘bay guys’ use to hack servers and stops them.

In this case it is thinking that your actions are suspicious and blocks them. This is actually quite common on WordPress when uploading large plugins. Of course, if you sure your plugin is safe and want to upload it this is a problem for you.

This is something that normally has to be fixed at host level, especially if you are on a shared server, where the hosting company may be very reluctant to reduce security.

However if you are on your own VPS or server than the steps are fairly easy.

First inspect your Apache log file for your site, normally error_log. You can do this visually ( looking for the words Mod Security and the value after id )or if you have shell access this command line is good.

grep ModSecurity path/to_my_domain/logs/error_log | sed -e 's#^.*\[id "\([0-9]*\).*hostname "
\([a-z0-9\-\_\.]*\)"\].*uri "#\1 \2 #' | cut -d\" -f1 | sort -n | uniq -c | sort -n

1 2	grep ModSecurity path/to_my_domain/logs/error_log \| sed -e 's#^.\[id "$[0-9]$.hostname " $[a-z0-9\-\_\.]$"\].*uri "#\1 \2 #' \| cut -d\" -f1 \| sort -n \| uniq -c \| sort -n

Which will give a result like

3 200004 example.com /wp-admin/update.php

1	3 200004 example.com /wp-admin/update.php

The next step is to compose this directive ( based on the above )

<LocationMatch "/wp-admin/update.php">
    SecRuleRemoveById 200004
</LocationMatch>

SecRuleRemoveById 200004

</LocationMatch>

And add it to the appropriate Apache .conf file. If your domain is a <VirtualHost> then just before the </VirtualHost> for your domain is appropriate.

If you want the rule to apply to all sites /etc/apache2/conf-available/security.conf might be more appropriate

Let me know where you put this on your system, please feel free to comment below.

Problem with WordPress 4.8 screwing up your website layout?

10th June 2017 by Alan Leave a Comment

WordPress 4.8 has just been released, and many web designers have reported that their layout have been mucked up with this release.

*** UPDATE ***

Since writing this blog post I have written a plugin – https://wordpress.org/plugins/add-paragraphs-option-to-text-widget/ – that solves this problem in a very neat way.

***

There could be multiple reasons for this, but one reason is that text widgets now always automatically add paragraphs to the html.

In theory, every thing should be OK if you don’t edit the text widget, but as soon as you do, any blank lines will get <p> inserted, and if for instance you are using the text widget for a <script> and there are blank lines the insertion of <p> will break the script.

Web developers have relied on the text widget to be able to add raw code, but no longer.

However there is a quick fix, that will stop paragraphs being insert, but it applies across all text widgets.

remove_filter( 'widget_text_content', 'wpautop' );

1	remove_filter( 'widget_text_content', 'wpautop' );

Add this to an appropriate place in your ( child ) theme’s functions.php

Of course, if this is a bit beyond you, you can contact me and I can quote to help support your WordPress site.

Hugo: I’m receiving the message “We were unable to load Disqus.”

28th April 2017 by Alan Leave a Comment

When building a Hugo site you may well get the message “I’m receiving the message “We were unable to load Disqus.” “

It took me a while to trouble shoot on mine.

Basically Hugo them developers have a habit of setting the baseurl in the config.toml as “/”

Your site will seem to work – but Disqus javascript needs the full url

So if you get the message from Disqus on your Hugo site saying it can load – set your baseurl to a the full domain e.g. https://example.com and clear your browser cache and try again.

The clue to the solution is at the very end of the Disqus help page https://help.disqus.com/customer/portal/articles/472007-i-m-receiving-the-message-%22we-were-unable-to-load-disqus-%22

Google Compute Engine Snapshot automation

22nd December 2016 by Alan Leave a Comment

Google Compute Engine comes with an incremental snapshot capability.

The product doesn’t have a specific automated method to take snapshots and to tidy them up either, but scripting using the gcloud command line is fairly straight forward, once you understand the power of the command line.

I have seen many attempts at automating this using bash scripts, python and even ruby, but in the main complex scripting isn’t actually required.

For my purpose I have used bash as the scripting language, but you will see that all is required is two simple loops and could be implemented in any scripting language that can execute commands.

Before we begin, you will need to have install the Google Cloud SDK which includes the gcloud command line interface (cli) this is available for most platforms here. https://cloud.google.com/sdk/downloads

Additionally, it is well worth understanding a bit about Persistent Disk snapshots, in the way they work incrementally.

Compute Engine stores multiple copies of each snapshot redundantly across multiple locations with automatic checksums to ensure the integrity of your data. You cannot share snapshots across projects.

If you delete snapshot 1 all the data in 1 gets migrated into snapshot 2. As it is incremental you are not really duplicating a lot of data, all depending on the volatility of the data on your server.

You would have to delete ALL snapshots for a disk to effectively start again, otherwise you are always building on the previous image. For systems that are relatively static this makes a very cost effective and simple snapshot solution.

Also read the part about consistent state of data. In a highly volatile data environment suspending updates and flushing data is important, for a more static environment (e.g. serving simple websites ) this is less so.

The use case for this script is to list all disks in a project ( regardless of what server they are mounted on ) and to take a snapshot.

The second function, is simply to delete older snapshots where granularity is no longer required, remember deleting old snapshots doesn’t lose data it just pushed it into the more recent snapshots. Strictly speaking there is no real need to delete snapshots, but too many would be unmanageble.

Therefore we need two loops.

The elements of loop 1 are:

gcloud compute disks list --format='value(name,zone)'

1	gcloud compute disks list --format='value(name,zone)'

Which lists all disks in a project – the format=’value(name,zone)’ forces the command to return a tab delimited list without headings, containing name & zone. There are other format options, see https://cloud.google.com/sdk/gcloud/reference/topic/formats , so you can choose what is best for you, but this works nicely with a bash loop.

then

gcloud compute disks snapshot $DISK_NAME --snapshot-names autogcs-$DISK_NAME-$(date "+%Y-%m-%d-%s") --zone $ZONE

1	gcloud compute disks snapshot $DISK_NAME --snapshot-names autogcs-$DISK_NAME-$(date "+%Y-%m-%d-%s") --zone $ZONE

which uses the list to create snapshots appropriately prefixed and named ( so we can find the ones created by the script.

The elements of loop 2 are:

gcloud compute snapshots list --filter="creationTimestamp<$(date -d "-60 days" "+%Y-%m-%d")" --regexp "(autogcs.*)" --uri

1	gcloud compute snapshots list --filter="creationTimestamp<$(date -d "-60 days" "+%Y-%m-%d")" --regexp "(autogcs.*)" --uri

Which lists all snapshots will a creation date less than, in this case, 60 days. This is driven by the –filter= expression, it seems that the filter handles dates and partial dates without any need for specific conversions. It also only lists snapshot with a prefix of “autogcs-” that we set earlier, to stop deleting other manual snapshots, this is done by the flag –regexp=”(autogcs.*)” (although I suspect that this could be incorporated into –filter). The final flag –uri returns a full path needed in the delete.

and then for each found

gcloud compute snapshots delete $SNAPSHOT_URI

1	gcloud compute snapshots delete $SNAPSHOT_URI

Which should be self explanatory.

If you would like the full bash script and also details on how to install and set up cron job you can find it here https://gitlab.com/alan8/google-cloud-auto-snapshot

Please leave any comments or suggestion below or at gitlab.

Using GIT to deploy scripts to production servers

21st December 2016 by Alan Leave a Comment

This is how I use GIT to deploy script configurations to multiple servers.

In this instance I have fail2ban configuration that I want to be able to deploy to multiple servers easily & quickly

I assume you are root – otherwise prefix commands with sudo as appropriate

I also assume that you have remote root ssh access ( by private / public keys is best of course )

Step 1 Install GIT if you don’t have it , e.g. on Debian

apt-get install git

1	apt-get install git

The key is to set up a GIT directory on the remote server and use the hook to deploy to the correct directory

cd /var
mkdir repo
mkdir f2ban.git && cd f2ban.git
git init --bare

cd /var

mkdir repo

mkdir f2ban.git && cd f2ban.git

git init --bare

We make a bare repo – the convention is a bare repo directory ends in git

Now we move to the hooks directory

cd hooks

cd hooks

And we need to create a file called post-receive that will process the files on being pushed here

The file needs to contain ( use vim or similar )

git --work-tree=/etc/fail2ban --git-dir=/var/repo/f2ban.git checkout -f

1	git --work-tree=/etc/fail2ban --git-dir=/var/repo/f2ban.git checkout -f

Basically saying when files come here – put them into the fail2ban directory

And post-receive need to be executable i.e.

chmod +x post-receive

1	chmod +x post-receive

On the localmachine in your git directory you need to add the remote server

git remote add myservername ssh://root@myprodserver/var/repo/f2ban.git

1	git remote add myservername ssh://root@myprodserver/var/repo/f2ban.git

And after normal git adding & committing you can push to your server e.g.

git push myservername master

1	git push myservername master

You can repeat this with different servers or different /var/repo/xxx.gits as rerequired

Submit A Post via Front End using Gravity Forms

7th December 2016 by Alan Leave a Comment

The following is a Gravity Form Form, that allows you to submit a post via the front end.

It can submit as ‘draft’, ‘pending review’ or even ‘published’.

Feel free to try it, and if you include a valid WordPress tip or other news I may even publish it.

How to Extract URLs from Google SERPs

21st October 2016 by Alan Leave a Comment

These steps are how to easily extract URLs from google SERPs

Install Chrome
Install Chris Ainsworth’s Extractor ‘bookmarklet’ http://www.chrisains.com/seo-tools/extract-urls-from-web-serps/
Install ginfinity plugin for Chrome https://chrome.google.com/webstore/detail/ginfinity/dgomfdmdnjbnfhodggijhpbmkgfabcmn
Set Google search to return 100 per page
Run the query
Click on the bookmark

This summarises the steps detailed and provided by Chris Ainsworth at http://www.chrisains.com/seo-tools/extract-urls-from-web-serps/

Backing up to gcloud storage from Linux/Virtualmin

5th August 2016 by Alan Leave a Comment

Using Google Cloud Storage as backup for your linux server is inexpensive if you use the nearline storage option. This is cheaper that Amazon Web Services (at the time of writing)

The process I use is as follows.

Backup locally
Create storage bucket / folders, set lifecycle
Script to move backups
find way to execute script

As I use Virtualmin as my control panel, the process details they way to use it from Virtualmin, but you can tailor to your own needs.

I’m assuming you have already signed up to Google Cloud Console and set up a project / billing as required.

The process uses a local backup copy and then moves / deletes it. So if you are limited in working space, you may need to divide you backups in to workable tranches.

You will need gstutils loaded load onto your server using the Google SDK https://cloud.google.com/sdk/docs/ and properly authorised – e.g. via gcloud init

1. Using virtualmin to create scheduled backups

e.g. creating backups into the local directory /home/backups/files

2. Make a Google Storage Bucket

You can use the Google Cloud Console to do this, but as you have the gsutil command and you will need to get used to it, here is how to do it from the CLI.

I’m assuming assuming here you want to store in EU but you can use US or ASIA as required for -l (location)

I recommend the ‘class’ to be ‘nearline’ as this is the cheaper option -c nl

(change mybucket to a unique name of course)

gsutil mb -c nl -l EU gs://mybucket/

1	gsutil mb -c nl -l EU gs://mybucket/

set life cycle e.g. 35 days to delete or as required, that way your storage bills won’t grow forever.

create rule file as below (35 days) and run

gsutil lifecycle set lifecycle_config.json gs://mybucket/

1	gsutil lifecycle set lifecycle_config.json gs://mybucket/

{
    "rule":
    [
      {
        "action": {"type": "Delete"},
        "condition": {"age":35 }
      }
    ]
}

{

"rule":

[

{

"action": {"type": "Delete"},

"condition": {"age":35 }

}

]

}

3. create script in /files/backups

#!/bin/bash
#today variable as YYYY-MM-DD
NOW=$(date +"%Y-%m-%d")
#Upload all files to our dated folder in the selected bucket
gsutil cp /home/backups/files/* gs://mybuckets/$1/$NOW
#Delete all the files after uploading them
rm /home/backups/files/*

#!/bin/bash

#today variable as YYYY-MM-DD

NOW=$(date +"%Y-%m-%d")

#Upload all files to our dated folder in the selected bucket

gsutil cp /home/backups/files/* gs://mybuckets/$1/$NOW

#Delete all the files after uploading them

rm /home/backups/files/*

Takes a folder argument allows different backups to use it within the same bucket (folders get created automatically)

e.g. /bin/sh /home/backups/upload.sh weekly

make sure your script is executable

sudo chmod +x /home/backups/upload.sh

1	sudo chmod +x /home/backups/upload.sh

4. find ways to execute script

With Virualmin this is easy, in schedule set command to run after backup

Recovering backups

Of course to recover backs requires copying locally and then restoring too – but with gsutil that is fairly easy.

list your weekly backups

gsutil ls gs://mybucket/weekly

1	gsutil ls gs://mybucket/weekly

e.g.

gs://mybucket/weekly/

gs://mybucket/weekly/2016-07-31

gs://mybucket/weekly/2016-07-25/

gs://mybucket/weekly/2016-08-05/

get the full directory (copy recursively) for 2016-08-05 back into /home/backups/files

gsutil -m cp -r dir gs://mybucket/weekly/2016-08-05/ /home/backups/files

1	gsutil -m cp -r dir gs://mybucket/weekly/2016-08-05/ /home/backups/files

Then restore (in my case using Virtualmin) in the normal way

Build and host a static website with Hugo and Google Cloud Storage

28th July 2016 by Alan Leave a Comment

WordPress is overkill for 90% of small business websites, especially if they are only every going to ask the web developer to make changes. Static websites used to be just that, static, but now it is possible to create static websites that are simple (relatively) to update dynamically. Hugo is a Golang project that has been built to take static websites to the next level.

It uses a ‘wiki’ style simple markup rather than html, and folder based system to enable content management and has the concept of posts, so can be used as a blog too.

see https://gohugo.io/

There is a growing collection of themes, so you don’t have to build from scratch if you don’t want to, see http://themes.gohugo.io/

Hugo has a half decent quick start tutorial here https://gohugo.io/overview/quickstart/

Editing your site is done locally on your PC using your favourite editor or IDE – I tend now to use Atom https://atom.io/

and then it is case of pushing it out to where ever you want to host it. You can host it anywhere really from a shared host, you own sever or wealth of other services – two obvious ones are Amazon Web services S3 and Google Cloud Storage.

Google Cloud Storage explains how to set up a Static Site here https://cloud.google.com/storage/docs/hosting-static-website

The process is essentially, download Google Cloud SDK (gsutil) if you haven’t got it on your PC https://cloud.google.com/sdk/docs/

CNAME you domain to c.storage.googleapis.com. at your DNS registrar

Now CNAME only works on sub domains, so you are ok for www.mydomain.com but not mydomain.com. One solution is to set a 301 redirect at your registrar to from the naked a domain to www and cname the www. However if you don’t have that facility CloudFlare allows you to CNAME the naked domain. ( They call it CNAME flattening ), and can also use Cloudflare to redirect the www. to the naked domain, so you have a perfect solution.

So for the moment whilst this work well for a subdomain I can’t see it being viable for a full website.

Create a bucket named the same as your domain (that has been verified with Google), build and copy your site and set access to public, specify the index & 404 file

hugo --theme=hugo_theme_that_you_use_change_this # hugo command to build
cd public         # move into the directory build by hugo
gsutil mb gs://mydomain.net    #   create a bucket  for your domain
gsutil cp -r .  gs://mydomain.net  # copy recursively all content
gsutil acl ch -r -u AllUsers:R gs://mydomain.net  # recursively give public read access
gsutil web set -m index.html -e 404.html gs://mydomain.net  # set the web root & error pages

hugo --theme=hugo_theme_that_you_use_change_this # hugo command to build

cd public # move into the directory build by hugo

gsutil mb gs://mydomain.net # create a bucket for your domain

gsutil cp -r . gs://mydomain.net # copy recursively all content

gsutil acl ch -r -u AllUsers:R gs://mydomain.net # recursively give public read access

gsutil web set -m index.html -e 404.html gs://mydomain.net # set the web root & error pages

And you are done.

I guess wrap that up in a little ‘release’ script to make it easy.

Next I’ll look at hosting Hugo sites on Amazon.

Please feel free to comment.

Badly Wired

Cloud solutions, technical snippets and other goodies

Recipe for a Raspberry Pi Kiosk

Ingredients

Preparation and Cooking time

Method

Preparation

First Boot

Basic Setup

Set up Wireless Access

Test SSH

Install all the software needed

Setting up the X window

Set up the Kiosk

Start it on login

Tidy up boot up messages

Back it up

Did I miss anything?

WordPress Plugin install fails with Forbidden, you don’t have permission to wp-admin/update.php on your server

Problem with WordPress 4.8 screwing up your website layout?

Hugo: I’m receiving the message “We were unable to load Disqus.”

Google Compute Engine Snapshot automation

Using GIT to deploy scripts to production servers

Submit A Post via Front End using Gravity Forms

How to Extract URLs from Google SERPs

Backing up to gcloud storage from Linux/Virtualmin

1. Using virtualmin to create scheduled backups

2. Make a Google Storage Bucket

3. create script in /files/backups

4. find ways to execute script

Recovering backups

Build and host a static website with Hugo and Google Cloud Storage

Categories

Subscribe to my Newsletter

Ingredients

Preparation and Cooking time

Method

Preparation

First Boot

Basic Setup

Set up Wireless Access

Test SSH

Install all the software needed

Setting up the X window

Set up the Kiosk

Start it on login

Tidy up boot up messages

Back it up

Did I miss anything?

1. Using virtualmin to create scheduled backups

2. Make a Google Storage Bucket

3. create script in /files/backups

4. find ways to execute script

Recovering backups

Categories

Tags

Subscribe to my Newsletter