Karl Becker karlbecker

## vagrant-vmware-tech-preview-apple-m1-pro.md

      
              1 file
            
          
              40 forks
            
          
              53 comments
            
          
              171 stars
            
          
                sbailliez
                / vagrant-vmware-tech-preview-apple-m1-pro.md
            
            
              Last active
              April 10, 2024 07:51
            
              
                Vagrant and VMWare Tech Preview 21H1 on Apple M1 Pro
              
          
    Vagrant and VMWare Tech Preview 21H1 on Apple M1 Pro

UPDATE November 20, 2022: VMWare Fusion 13

VMWare Fusion 13 is now released. Read Vagrant and VMWare Fusion 13 Player on Apple M1 Pro for the latest.
Summary

This document summarizes notes taken while to make the VMWare Tech preview work on Apple M1 Pro, it originated

  
## NOTES.md

      
              1 file
            
          
              6 forks
            
          
              13 comments
            
          
              14 stars
            
          
                fatso83
                / NOTES.md
            
            
              Created
              October 9, 2021 07:31
            
              
                Installing Vagrant on Apple Silicon Macs (M1, M1X, etc)
              
          
    VirtualBox only supports the x86 platform, so the default installation instructions for Vagrant does not work
on Apple silicon. Thankfully Vagrant has a VMWare Provider
(more on providers here), and so if I can get VMWare running on
my M1 MacBook, I should be able to run Vagrant as well!
These are my notes during figuring this out.
Get the VMWare Tech Preview released in September 2021!

We are in luck, as VMWare released this just a few weeks ago.

See [their blog entry][1]


## up-and-running.md

      
              1 file
            
          
              0 forks
            
          
              2 comments
            
          
              5 stars
            
          
                pbiggar
                / up-and-running.md
            
            
              Last active
              January 31, 2017 10:27
            
              
                Getting your CircleCI builds up and running again
              
          
    In order to get your builds working again, we need to reauthenticate with GitHub and other services used in your build.
Logging in

When you log in to CircleCI via GitHub's OAuth, we get an API key to call the GitHub API, update the GitHub commit status, list your projects on the add projects page, etc.
We revoked all OAuth tokens to protect your GitHub repositories. The first time you log in to Circle, you'll have to reauthenticate the Circle GitHub application to get a new token.
The checkout phase


## gist:4062929

      
              1 file
            
          
              52 forks
            
          
              4 comments
            
          
              116 stars
            
          
                olivierlacan
                / gist:4062929
            
            
              Last active
              February 10, 2024 10:57
                — forked from Gregg/gist:968534
            
              
                Code School Screencasting Framework
              
          
    Screencasting Framework

The following document is a written account of the Code School screencasting framework.  It should be used as a reference of the accompanying screencast on the topic.
Why you should care about screencasting?

You're probably aren't going to take the time to read this document if you're not interested, but there are a lot of nice side effects caused by learning how to create quality screencasts.

Communicating more effectively - At Envy Labs we produce screencasts for our clients all the time.  Whether it's demoing a new feature or for a presentation for an invester, they're often much more effective and pleasent than a phone call or screen sharing.


## gist:3702830
function cc-tool-w {
  cc-tool --erase --write "$@" --verify && cc-tool --read-mac-address
}

## uri.js
var parser = document.createElement('a');
parser.href = "http://example.com:3000/pathname/?search=test#hash";

parser.protocol; // => "http:"
parser.hostname; // => "example.com"
parser.port;     // => "3000"
parser.pathname; // => "/pathname/"
parser.search;   // => "?search=test"
parser.hash;     // => "#hash"
parser.host;     // => "example.com:3000"
	function cc-tool-w {
	cc-tool --erase --write "$@" --verify && cc-tool --read-mac-address
	}
	var parser = document.createElement('a');
	parser.href = "http://example.com:3000/pathname/?search=test#hash";

	parser.protocol; // => "http:"
	parser.hostname; // => "example.com"
	parser.port; // => "3000"
	parser.pathname; // => "/pathname/"
	parser.search; // => "?search=test"
	parser.hash; // => "#hash"
	parser.host; // => "example.com:3000"