dleidert

REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Classes\SystemFileAssociations\text\shell\edit\command /f /ve /t REG_EXPAND_SZ /d "\"^%ProgramFiles^%\Notepad++\notepad++.exe\" %1"

dleidert

REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Classes\SystemFileAssociations\text\shell\edit\command /f /ve /t REG_EXPAND_SZ /d "\"^%ProgramFiles^%\Notepad++\notepad++.exe\" %1"

This will overwrite the default value!

dleidert

REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Classes\SystemFileAssociations\.html\shell\edit\command /f /ve /t REG_EXPAND_SZ /d "\"^%ProgramFiles^%\Notepad++\notepad++.exe\" %1"

This will create a new key and add an Edit option to the file context menu!

dleidert

This will prevent AppVeyor from running a job, when commits are done regarding the docs directory only. It might be useful, when the projects repository contains the GitHub pages in the master branch and changes to them are not critical to the build.

skip_commits:
  files:
    - docs/**/*

I further exclude some other files too. This is my minimal list

dleidert

{%- assign releases = site.github.releases | where: "draft", false | sort: "tag_name" | reverse -%}

## [UNRELEASED]({{ site.github.repository_url }}/tree/master/)

[compare changes to last release]({{ site.github.repository_url }}/compare/{{ releases[0].tag_name }}...master#files_bucket "Compare changes in master for upcoming release")

{% for release in releases limit:5 %}

## [{{ release.name }}]({{ release.html_url }}) {% if release.prerelease -%}(pre-release){%- endif %}

dleidert

TRAVIS builds are triggered by every commit to the repository. When hosting github pages with the source (e.g. in the docs folder), changes to the documentation are (usually) not critical to the build itself, so they could be easily skipped. Unfortunately TRAVIS does not offer a file-/foldername-based skip instruction like e.g. AppVeyor's skip_commits field.

But there seem to be two ways of achieving (almost) the same effect. In the following examples changes to the files

.appveyor.yml
.gitattributes
.gitignore
docs/**

dleidert

---
layout: default
title: Debug site.github
---

```JSON
{{ site.github | neat_json }}
```

dleidert

Below is an example for a jekyll template to provide structed data in JSON-LD for a software application using the site.github namespace (provided by the github-metadata) plugin). Assuming there is at least one release, this snippet is a starting point. Content represented by three dots ... usually needs to be added manually to the snippet:

{%- assign release = site.github.latest_release -%}
{
  "@context": "http://schema.org/",
  "@type": "SoftwareApplication",
  "codeRepository": "{{ repository_url }}",
  "programmingLanguage": {
    "@type": "ComputerLanguage",

dleidert

Setting up TRAVIS CI for GitHub Pages

I recently set up TRAVIS CI support for my personal github pages. There are some github and jekyll support pages, that cover the basics. Unfortunately I ran into several build failures and issues not covered there until the builds finally succeeded. The following sections cover the issues and their solutions.

The results can be seen here: https://travis-ci.org/dleidert/dleidert.github.io/builds. I'm planning to add support for different ruby versions. This will probably require different Gemfile variants.

**Please note, that I don''t use TRAVIS to deploy the res

dleidert

<p>This is a general documentation of how to attempt an upgrade from OMV 2 to OMV 3 including an upgrade of the underlying operating system to Debian Jessie (8). This document does not claim to be complete. It is provided to the public "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. It is assumed that the operating system has not been heavily altered. So if you have installed a desktop environment, if you are using disk encryption, if you have self-written Init scripts, if you are running the system in a container, etc. make sure you read the <a href="https://www.debian.org/releases/jessie/amd64/release-notes/">release notes of Debian Jessie</a> in full and prepare yourself for the changes affecting your system. This document will cover just the basics and common configurations. It is assumed that there is either local or remote (SSH) access to the machine in question. For the latter it