betolink

/*

2013-07-23 @betolink
Modified from TrackBallControls to handle Three.js r59 API and not whole DOM attachment.
Licensed under WTFPL
http://www.wtfpl.net/txt/copying/

*/

THREE.TrackballControl = function ( object, domElement ) {

betolink

[
    {
        "class": "label_control",
        "color": [255, 255, 255],
        "shadow_color": [24, 24, 24],
        "shadow_offset": [0, -1]
    },
    {
        "class": "button_control",
        "content_margin": [6, 5, 6, 6],

betolink

# Use Xft?
use_xft yes
xftfont DejaVu Sans:size=8
xftalpha 0.8
text_buffer_size 2048

# Update interval in seconds
update_interval 1

betolink

nsidc-fetch-dispatch

---

Motivation

betolink

Keybase proof

I hereby claim:

• I am betolink on github.
• I am betolink (https://keybase.io/betolink) on keybase.
• I have a public key ASB81F0BgCwUkkyDzMyhTpj4XJ_W5XRwEpvFHstVyjIzJAo

To claim this, I am signing this object:

betolink

Fallacy #1. The network is reliable

• Why the pattern Client-Response might cause some troubles?
• What are distributed objects?
• How we can solve this problem?

Fallacy #2. Latency isn't a problem

• How many calls do you do between services before replying a syncronous call to the end user?
• Which pattern is more common in your application? Remote calls or messages?

betolink

NSIDC Cryohub @ AWS

A guide to deploy Jupyterhub using Kubernetes on AWS.

1. Overview
2. Cloud resources
3. Setup AWS credentials and environment variables
4. Configure a Kubernetes cluster on AWS
5. Deploy Jupyterhub to the cluster using Helm (PENDING)
   • config.yaml
   • authentication

betolink

betolink

betolink

Keybase proof

I hereby claim:

• I am betolink on github.
• I am betolink (https://keybase.io/betolink) on keybase.
• I have a public key ASCrY4QgiSsT5118Gwg4zNt8PZ15xR9Lr-no1-NYaiSONwo

To claim this, I am signing this object: