- Save the
docker-compose.ymlandconfig.ymlin the same directory on one of your volumes on the NAS. - SSH in and use
docker-compose up -d - Test the mirror with
curl --head http://NAS-IP:55000 - Start up docker daemons with the following option or put this in the daemon config file or copy into Docker for Mac/Windows settings.
--registry-mirror=http://NAS-IP:55000 - Pull an image and then check that it is cached in your mirror with
curl http://NAS-IP:55000/v2/_catalog- or check that a large image isn't slow after the first pull :)
| $destinationDirectory = "C:\LocalNuGetTest\" | |
| $webClient = New-Object System.Net.WebClient | |
| $webClient.Credentials = New-Object System.Net.NetworkCredential("USERNAME", "PASSWORD") | |
| $feed =[xml]$webClient.DownloadString("https://hostednugetfeed.com/custom-feed/nuget/v2/Packages") | |
| $records = $feed | select -ExpandProperty feed | select -ExpandProperty entry #| select -ExpandProperty content | |
| for ($i=0; $i -lt $records.Length; $i++) { | |
| $content = $records[$i] | select -ExpandProperty content | |
| $properties = $records[$i] | select -ExpandProperty properties |
| -- My own config file to get the Hyper Key working again with my current setup. | |
| -- All credit goes to @prenagha and @ttscoff for their awesome original code that I tweaked for my own devices. | |
| -- Credit 1: https://gist.github.com/ttscoff/cce98a711b5476166792d5e6f1ac5907 | |
| -- Credit 2: https://gist.github.com/prenagha/1c28f71cb4d52b3133a4bff1b3849c3e | |
| -- A global variable for the sub-key Hyper Mode | |
| k = hs.hotkey.modal.new({}, 'F17') | |
| -- Hyper-key for all the below are setup somewhere... Usually Keyboard Maestro or similar. Alfred doesn't handle them very well, so will set up separate bindings for individual apps below. |
This guide will show you how to install and configure elementaryOS Loki on your Acer C720 or C720p. I'm assuming you have installed some sort of Linux on your Chromebook before and already know your way around in Developer Mode. If not, read and follow https://www.chromium.org/chromium-os/developer-information-for-chrome-os-devices/acer-c720-chromebook sections "Developer Mode" and "Legacy Boot".
Nothing special here: Download the ISO from https://elementary.io (put in $0 as an amount to download the ISO for free, although you should consider donating)
| -- hattip https://github.com/lodestone/hyper-hacks | |
| -- hattip https://gist.github.com/ttscoff/cce98a711b5476166792d5e6f1ac5907 | |
| -- A global variable for the sub-key Hyper Mode | |
| k = hs.hotkey.modal.new({}, 'F18') | |
| -- Hyper+key for all the below are setup somewhere | |
| -- The handler already exists, usually in Keyboard Maestro | |
| -- we just have to get the right keystroke sent |
| -- A global variable for the Hyper Mode | |
| k = hs.hotkey.modal.new({}, "F17") | |
| -- Trigger existing hyper key shortcuts | |
| k:bind({}, 'm', nil, function() hs.eventtap.keyStroke({"cmd","alt","shift","ctrl"}, 'm') end) | |
| -- OR build your own | |
| launch = function(appname) |
| # Image neeeds to have ssh-client | |
| image: docker:git | |
| services: | |
| - docker:dind | |
| stages: | |
| - staging | |
| before_script: | |
| - docker login -u gitlab-ci-token -p $CI_BUILD_TOKEN $CI_REGISTRY |
NOTE: This Gist was an early write-up of this blog post, part of what became an eleven-part series on my arcade cabinet. I'd suggest you read that post instead of this, but some of the comments on this Gist contain updates and field reports that you might find useful.
I wanted LEDBlinky-style functionality out of my RetroPie cabinet. But I didn't need RGB control or magical frontend integration or anything like that. I had buttons with simple single-color LEDs.
I've got a simple control panel with six buttons per player. All I wanted was this:
- When I launch Street Fighter 2, all twelve buttons should light up.
- When I launch The Simpsons, only the first two buttons for each player should light up.
You can now read this on my (pretty) website! Check it out here.
Every reason to get more HackerPoints™ is a good one, so today we're going to
write a neat command line app in .NET Core! The Common library has a really cool
package Microsoft.Extensions.CommandlineUtils to help us parse command line
arguments and structure our app, but sadly it's undocumented.
No more! In this guide, we'll explore the package and write a really neat
| { | |
| "presets": ["es2015"], | |
| "plugins": ["transform-runtime"] | |
| } |