Gist 3696816

100%

✓ Published0🌍 Public

Last edited Sep 11, 2012

Created on Sep 11, 2012

This shell function shows how to enumerate server details across an Engine Yard environment by opening an SSH session to each server and querying instance metadata. It displays the hostname, instance ID, and public hostname for every server in the specified environment, defaulting to “stipple_prod” and all servers if no arguments are given. The function uses the `ey` command-line tool for SSH access and `curl` to fetch instance metadata from the AWS EC2 metadata service at 169.254.169.254, combining the results with backticks for command substitution.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 5219363

This shell script demonstrates how to map EC2 instances to their environment and server scope by querying the AWS instance metadata service. It uses `curl` to retrieve the instance ID and public hostname from the metadata endpoints at 169.254.169.254, then combines them with the `hostname` command and passes the result to the `ey` CLI tool via SSH. The script supports optional arguments for environment and server scope, defaulting to “stipple_prod” and “--all”, and illustrates a practical command-line workflow for infrastructure diagnostics.

XXXX

81% match

Loading thumbnail…

Gist 39225

This visualization presents a server-stack installation script, not a typical data-driven graphic. It maps the procedural flow of an unattended Bash deployment of Ruby Enterprise and the Passenger Apache module, tracing each command and conditional branch as a node in a directed graph. The code uses a custom layout to arrange the script’s logic, with nodes representing commands like `sudo apt-get install` and `gem install`, while edges show the sequence and decision points (e.g., `if [ -e $REEF ]`). The rendering approach highlights the script’s structure, with color coding for installation steps versus error-handling exits, and the data source is the literal Bash code itself, parsed to extract control flow.

DDylanFM

58% match

Loading thumbnail…

Gist 4c5c3a03de2d3fea691e3fc9b4995d84

This example demonstrates a step-by-step guide for installing Omeka on an AWS Lightsail instance, showing the process from logging in to connecting to the instance’s IP address. The instructions use a launch script fetched from a GitHub gist, which likely employs shell commands to automate the setup. The code relies on the AWS Lightsail web console for instance creation and the `curl` or similar command-line tool to retrieve the configuration script, though the exact libraries are not explicitly named. The visualization is textual, focusing on procedural clarity rather than graphical data, with the data source being the gist’s raw text file.

CCliffordAnderson

56% match

Loading thumbnail…

To connect to EC2 env in a SSH Client, the following Gist has to be updated for a specific machine, source and final folders and also the Pub file.

This example shows a shell-based workflow for connecting to an Amazon EC2 instance from an SSH client, including transferring a public key and syncing local folders. It uses command-line tools like `pscp`, `ssh`, `ssh-keygen`, and `scp` to convert a PuTTY key, append the client’s public key to the server’s `authorized_keys`, and copy files via SCP with strict host checking disabled. The gist exposes the necessary commands and file paths that must be edited per machine.

PP7h

55% match

Loading thumbnail…

Gist 209613

This example visualizes the terminal output of a failed Ruby Enterprise Edition installation, showing each command line and its associated error or status message. The data comes from a gist file containing the raw shell session text. It uses d3.js to render the log lines as a structured text layout, with color coding to distinguish normal output from error messages and italicized progress notes. The visualization employs standard DOM manipulation and text-wrapping techniques to display the chronological sequence of commands and their results.

XXXX

54% match

Loading thumbnail…

Gist 0711211684d6b9f38dc69fe06a29d844

This example shows a shell script that automates the setup of a Linux scavenger hunt lab environment by downloading a deploy key, cloning a GitLab repository, and running Vagrant to provision the machine. The script uses `curl` to fetch an SSH key, `git clone` with submodules to pull the lab definitions, and `vagrant up` to launch the virtual machine. It then extracts the SSH hostname and port from `vagrant ssh-config` using `grep` and `awk`, printing connection instructions for the student user.

PPeleke

53% match

Loading thumbnail…

Gist a9811ea9c0293f1b19277f7a6995b236

This example shows a bash script that automates the setup of a Linux scavenger-hunt lab environment. It downloads an SSH deploy key, clones a Git repository from GitLab, initializes submodules, and uses Vagrant to provision the virtual machine. The script concludes by parsing `vagrant ssh-config` output with `awk` and `sed` to display the student’s SSH connection details, including hostname and port.

PPeleke

52% match

Loading thumbnail…

Gist 79abf411748d1f79ce072fdc8d879407

This example scripts the automated deployment of a Linux scavenger-hunt lab environment. It downloads a private SSH key from a gist, clones a GitLab repository with submodules, and provisions the machine with Vagrant. It then parses `vagrant ssh-config` output to extract the hostname and port, printing the final SSH connection command for the student.

PPeleke

52% match