Skip to content

Instantly share code, notes, and snippets.

View joelpittet's full-sized avatar

Joel Pittet joelpittet

44 followers · 29 following
View GitHub Profile
@joelpittet
joelpittet / vagrant-nfs-vpn-solution.md
Last active October 6, 2018 00:20 — forked from johnkary/vagrant-nfs-vpn-solution.md
Workaround for using an NFS mount with Vagrant and VirtualBox while connecting to a VPN network restricting local network connections

Fixing NFS disconnecting with Vagrant and VirtualBox on Mac OS

Symptoms and Known Conditions

  • Mac OS host machine (10.6+)
  • VirtualBox (4.1+)
  • Vagrant (1.0+)
  • Connecting via VPN to a remote network
  • Mounting a directory from your host machine to the guest machine using NFS with something like this:



  


  




    


          
    

      

        
        

          

              @joelpittet
          

          

            
                joelpittet
                / openconnect.md
            
            

              Created
              October 6, 2018 00:11
                — forked from moklett/openconnect.md
            

              
                OpenConnect VPN on Mac OS X
              
          

        

      

        

  

      

    
Unfortunately, the Cisco AnyConnect client for Mac conflicts with Pow. And by "conflicts", I mean it causes a grey-screen-of-death kernel panic anytime you connect to the VPN and Pow is installed.


As an alternative, there is OpenConnect, a command-line client for Cisco's AnyConnect SSL VPN.


Here's how to get it set up on Mac OS X:


    

  1. 

    OpenConnect can be installed via homebrew:
    

     brew update

    

    2. 



brew install openconnect



  


  




    


          
    

      

        
        

          

              @joelpittet
          

          

            
                joelpittet
                / mysql-utf8mb4-barracuda
            
            

              Created
              November 7, 2015 01:26
                — forked from v1nc3ntlaw/mysql-utf8mb4-barracuda
            

              
                MySQL using utf8mb4 and innodb_file_format Barracuda settings
              
          

        

      

        

  

    
    


        



  


  

        

          
          [mysqld]
        

        

          
          

        

        

          
          init_connect='SET collation_connection = utf8mb4_unicode_ci'
        

        

          
          init_connect='SET NAMES utf8mb4'
        

        

          
          character-set-server  = utf8mb4
        

        

          
          character-set-client  = utf8mb4
        

        

          
          collation-server      = utf8mb4_unicode_ci
        

        

          
          skip-character-set-client-handshake
        

        

          
          

        

        

          
          innodb_file_format     = Barracuda
        

  





    


  




    


          
    

      

        
        

          

              @joelpittet
          

          

            
                joelpittet
                / Vertically-center-image-within-responsive-container.markdown
            
            

              Last active
              August 29, 2015 14:08
                — forked from anonymous/Vertically-center-image-within-responsive-container.markdown
            

          

        

      

        

  

      

    
  


  




    


          
    

      

        
        

          

              @joelpittet
          

          

            
                joelpittet
                / classes.twig
            
            

              Created
              July 3, 2014 05:31
                — forked from markhalliwell/classes.twig
            

          

        

      

        

  

    
    


        



  


  

        

          
          {% attributes.class.add([
        

        

          
            'node',
        

        

          
            'node--type-' ~ node.bundle|class,
        

        

          
            node.promoted ? 'node--promoted',
        

        

          
            node.sticky ? 'node--sticky',
        

        

          
            not node.published ? 'node--unpublished',
        

        

          
            preview ? 'node--preview',
        

        

          
            'node--view-mode-' ~ view_mode|class
        

        

          
          ]).remove([
        

        

          
            'some-module-class'
        

  





    


  




    


          
    

      

        
        

          

              @joelpittet
          

          

            
                joelpittet
                / Contract Killer 3.md
            
            

              Created
              December 3, 2013 03:39
                — forked from malarkey/Contract Killer 3.md
            

          

        

      

        

  

      

    
Contract Killer 3


Revised date: 07/11/2012


Between us [company name]
and you [customer name]


Summary:


We’ll always do our best to fulfil your needs and meet your expectations, but it’s important to have things written down so that we both know what’s what, who should do what and when, and what will happen if something goes wrong. In this contract you won’t find any complicated legal terms or long passages of unreadable text. We’ve no desire to trick you into signing something that you might later regret. What we do want is what’s best for both parties, now and in the future.