Rob McGinley mcginleyr1

## 00-README.md

      
              4 files
            
          
              1 fork
            
          
              1 comment
            
          
              4 stars
            
          
                imbriaco
                / 00-README.md
            
            
              Last active
              May 26, 2018 08:02
            
              
                Example deployment descriptor for running Cog on Kubernetes. Uses the secret store as well as persistent disks for Postgres, Cog, and Relay data.
              
          
    Cog on Kubernetes

This experiment was originally built on Google Cloud's Kubernetes and makes use of gcePersistentDisk.
If you are not using Google Cloud, you'll need to adjust the gcePersistentDisk volumes to use the
persistent disk technology available in your cluster.
At a high level the steps look something like this, though there may be subtle errors. This experiment
happened a few weeks ago and I'm creating these from memory along with the test descriptors I used.

Setup Kubernetes and create the necessary persistent disks that are referenced in the deployment.


## horr.erl
-module(horr).
-export([malloc/0, free/1, read/1, write/2, test/0]).

% You can use `malloc` to get a globally sharable, mutable cell of memory.
% A difference to C's `malloc` is that such a cell doesn't have a certain size (you can't overflow)
% Memory is initialised with the atom `null`.
malloc() ->
    spawn(fun() -> mem(null) end).

% As processes are not garbage collected, you have to call `free` when you're done with your memory:

## remotepaste.md

      
              1 file
            
          
              21 forks
            
          
              14 comments
            
          
              127 stars
            
          
                burke
                / remotepaste.md
            
            
              Last active
              September 26, 2023 11:04
            
              
                This sets up keybindings in tmux that allow you to copy/paste to/from your OS X clipboard from tmux running inside an SSH connection to a remote host. Partially borrowed from http://seancoates.com/blogs/remote-pbcopy
              
          
    Local (OS X) Side

~/Library/LaunchAgents/pbcopy.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
     <key>Label</key>
     <string>localhost.pbcopy</string>

  
## chicken.rb
###
# Scheme code is translated to YARV byte code, then evaluated in the
# Ruby Virtual Machine

require 'rbconfig'
require 'dl'
require 'fiddle'
require 'strscan'

class RubyVM

## retries.py
#!/usr/bin/env python
#
# Copyright 2012 by Jeff Laughlin Consulting LLC
#
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
	-module(horr).
	-export([malloc/0, free/1, read/1, write/2, test/0]).

	% You can use `malloc` to get a globally sharable, mutable cell of memory.
	% A difference to C's `malloc` is that such a cell doesn't have a certain size (you can't overflow)
	% Memory is initialised with the atom `null`.
	malloc() ->
	spawn(fun() -> mem(null) end).

	% As processes are not garbage collected, you have to call `free` when you're done with your memory:
	###
	# Scheme code is translated to YARV byte code, then evaluated in the
	# Ruby Virtual Machine

	require 'rbconfig'
	require 'dl'
	require 'fiddle'
	require 'strscan'

	class RubyVM
	#!/usr/bin/env python
	#
	# Copyright 2012 by Jeff Laughlin Consulting LLC
	#
	# Permission is hereby granted, free of charge, to any person obtaining a copy
	# of this software and associated documentation files (the "Software"), to deal
	# in the Software without restriction, including without limitation the rights
	# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
	# copies of the Software, and to permit persons to whom the Software is
	# furnished to do so, subject to the following conditions: