joesepi

# Sublime package NVM node path configuration
# Save this file in:
# ~/Library/Application\ Support/Sublime\ Text\ 3/Packages/node_env.py
import os

os.environ["PATH"] = "/Users/YOUR_USERNAME/.nvm/v0.10.26/bin:/Users/cranemes/.nvm/v0.10.26/lib:/Users/YOUR_USERNAME/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"
print("PATH=" + os.environ["PATH"])

joesepi

var http = require("http"),
    url = require("url"),
    path = require("path"),
    fs = require("fs")
    port = process.argv[2] || 8888;

http.createServer(function(request, response) {

  var uri = url.parse(request.url).pathname
    , filename = path.join(process.cwd(), uri);

joesepi

Meric - 

Joe, Erin and I were speaking and we wanted to make sure we were being clear about some of our thoughts in regards to a proposed LB API vs APIC.
If you already understand what I'm saying, please forgive us, we just feel it's important to ensure folks understand where we're coming from.

You've asked about the capabilities of the APIC CLI vs slc. While I've found that a LB developer *could* make use of the APIC CLI (especially with the modifications I suggested), 
we want to be clear that our argument for a proper LB CLI is *not* about features. It is about using the *appropriate* tool for the job.

APIC is not appropriate for LB developers for two main reasons: