iPad Keyboard Commands for gcloud web-based ssh terminal (vi w/ Zagg bluetooth keyboard)

2015-06-30 09.37.44

Escape: ALT or OPTION + “[” (left bracket)
Up: k
Down: j
Left: h
Right: l (lowercase L)
Bonus: tab completion can be accomplished via CTRL+tab.

I’ve been playing around with Google Compute Engine and setting up a development environment on my iPad. A requirement for the sysadmin side of the process is vi. From a terminal app on a Mac or PC, this is cake. From the web-based SSH client on an iPad, you have to use the old school keyboard commands instead of the arrows, ESC, and TAB. I use this Zagg bluetooth keyboard case.

I’ll probably cover the complete dev setup in another post, but if you’re curious here’s a summary:

– Server admin and Apache/Node configs: Open the Compute Engine instance in the web and open the web-based SSH client.

– Code editing and development: Textastic iOS app, using Dropbox.

– Code versioning and repositories: A server is sync’d with Dropbox and file changes trigger a git commit and push to GitHub. Merges and branch changes are done via web-based terminal.

– Continuous Integration: After GitHub commits, an HTTP POST is automatically sent to the deploy server. It retrieves and applies the applicable version from GitHub. (note: I may switch to Chef, but for now this “just works”).

Amazon AWS releases CloudFront – here’s how it works

Amazon released CloudFront to public beta today. It’s a simple way to get free content publicly available to the edge of the network (closest to the recipient downloader).

From the AWS announcement:

Amazon CloudFront is a web service for content delivery. It integrates with other Amazon Web Services to give developers and businesses an easy way to distribute content to end users with low latency, high data transfer speeds, and no commitments.

Here’s how it works:

  1. Upload your content files to S3.
  2. Call the CloudFront API, specifying the S3 bucket.
  3. Use your S3 bucket’s already created domain and filename in your website (no change here).
  4. When a customer clicks a link the closest file is automatically routed.

So, uhhh, what’s special here? From AWS’s description, CloudFront is simply setting a flag for your S3 bucket that means it’s to be distributed around the cloud or remain in a single location.

This should be an addition to the S3 service, not a separate service. The added step of having to let CloudFront know you want the edge network coverage is an unnecessary chore. It would be better as an attribute for the S3 bucket. This would make S3 a stronger brand, keep it clearer for those navigating AWS, and simplify the process of pushing content (1 less step).

Here’s how much it costs:
Continue Reading