EugeneKay

NOTE: This Gist concerns the old Linode KVM Beta, NOT the current Manager. Please see linode/docs#501 (comment) for more up-to-date instructions.

You will need:

• Windows Server 2012 R2 iso. Obtain from MSDN
• A server with libvirt/virt-manager/KVM/etc set up.
• Fedora-sourced Windows virtio drivers: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.103-2/virtio-win-0.1.103.iso
• A Linode 1GB in the KVM beta, booted into Rescue mode, with a 20GB(20480MB) "raw" image.

On the KVM source, run the following to create a VM:

kenkeiter

/////////////////////////////////////////////////////////
// Copied from http://www.alecjacobson.com/weblog/?p=3816
/////////////////////////////////////////////////////////
#import <Foundation/Foundation.h>
#import <Cocoa/Cocoa.h>
#import <unistd.h>
BOOL copy_to_clipboard(NSString *path)
{
  // http://stackoverflow.com/questions/2681630/how-to-read-png-image-to-nsimage
  NSImage * image;

jpierson

If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.

To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.

1. Clone some repo (you've probably already done this step)

   git clone git@github...some-repo.git

walt

{
  "version": "https://jsonfeed.org/version/1",
  "title": "<$mt:BlogName smarty_pants="1" remove_html="1" escape_for_json="1"$>",
  "home_page_url": "<$mt:BlogURL$>",
  "feed_url": "<$mt:BlogURL$>feed.json",
  "description": "<$mt:BlogDescription smarty_pants="1" remove_html="1" escape_for_json="1"$>",
  "favicon": "<$mt:BlogURL$>favicon.ico",
  "items": [
<mt:Entries lastn="5">
    {

JoeyBurzynski

58 bytes of CSS to look great nearly everywhere

When making this website, i wanted a simple, reasonable way to make it look good on most displays. Not counting any minimization techniques, the following 58 bytes worked well for me:

main {
  max-width: 38rem;
  padding: 2rem;
  margin: auto;
}