- In
/opt/bootsync.shreplace the linesethostname=with the preferred host name preferred - Save changes:
filetool.sh -b
These are the steps taken to have Sonarr, Radarr & Lidarr on piCore 9.0.3 running Mono 4.4.2
Newer version might work as well (or maybe even better), but have not been tested.
- Download the piCore image
- Unpack the
.zipfile and write the.imgfile to the SD-Card (using USB Image Tool for example) - Move the SD-Card to the Pi, plug the Pi into the network and plug in the power source
- SSH into the Pi (using Putty for example)
- Make sure your git-templates directory is correctly set:
git config --global init.templatedir "~/.git-templates" - Create a
.git-templatesdirectory in your user directory (C:\Users\usernameon Windows) - Add a subdirectory
hooks - Download the
pre-commitfile to the created directory
On every git init and git commit the hooks will be copied over to the new repository.
Whenever a git commit is issued, the pre-commit hook will check if the user.name and user.email are set, if not, it will ask for input.
- Download the portable version of GitExtensions
- Unpack the downloaded file to a sensible location (
C:\Program Files (x86)\for example) - Apply configuration to git:
git config --global core.editor "\"C:\path\to\GitExtensions.exe\" fileeditor"
| #!/usr/bin/env python | |
| # This script takes keyboard input and uses it to send events to the Kodi eventserver, | |
| # it can be installed on any small pc like a Pi. | |
| # To use an ordinary remote one could a Flirc. | |
| # (the eventserver will be started automaticly when Kodi starts) | |
| # It is assumed the keyboard is at /dev/input/event0 | |
| # The IP address connected to need to be adjusted to your Kodi installation | |
| # The XBMCClient class is used and can be found in the official Kodi repo | |
| # To get the evdev library you'll need pip: apt-get install python-pip python dev |
This is a description on how I got my Kodi (OSMC to be specific) set up on my Raspberry Pi. Documented here in case anything goes wrong and I got to do it all over again. Obviously this is not a headless installation, so a screen and a way to do some input it assumed 😉
- Get the latest RPi2 disk image from OSMC.tv, write the image to an (Micro)SD-card, put the card in the Pi and boot
- After the first boot it will ask to input the language, timezone, optionally a device name, SSH access (best to be turned on), network settings and what skin you like (I prefer to start with
Classic). MySQL settings for the master profile can be set already as well - Go to
My OSMC->Updates->Manual controls, start a scan for updates and install if necessary - Go to
My OSMC->Networkto set a static ip if not done at first boot - Go to System (settings) ->
Live TV Settings->Playbackand disableStart playback minimised
(The commands have been copied over from raspberry-at-home.com/logitech-media-server, and updated when necessary. Tested on Raspbian Jessie)
sudo apt-get update && sudo apt-get dist-upgradesudo apt-get install libsox-fmt-all libflac-dev libfaad2 libmad0
wget http://downloads.slimdevices.com/nightly/7.9/sc/481dece/logitechmediaserver_7.9.0~1485931015_arm.deb
sudo dpkg -i logitechmediaserver_7.9.0~1485931015_arm.deb
- Download the Raspbian Light image and write it onto an SD
- Add an empty
sshfile to thebootpartition - SSH into the Pi
- Update the system:
sudo apt-get updatesudo apt-get upgrade
- Create a new gear on OpenShift
- Copy the GIT url of the gear
- Start up Orion and open up the
Gittab - Get yourself a SSH key from lagmonster.org/keygen.php
- Go to your OpenShift settings and add a new
public key(name it Orion for example) - At Orion add a new Git project using the url of your OpenShift gear and the
private key
- Stage the files for commit (
git addthe files) - Write the tree (this only creates a tree object, returning the SHA of the new tree):
git write-tree- Optionally: examine the new tree:
git ls-tree [SHA]
- Optionally: examine the new tree:
- Create the commit:
git commit-tree [SHA] -p [PARENT-SHA] -m "Commit message"(add as many seperate-p [PARENT-SHA]as you want (makes it look like a merge))
The SHA of the new commit will be given to you on succes - Finally, merge the new commit into you branch
git merge [NEW-SHA]