| # vim:syntax=perl | |
| #------------------------------------------------------------------- | |
| # WebGUI is Copyright 2001-2009 Plain Black Corporation. | |
| #------------------------------------------------------------------- | |
| # Please read the legal notices (docs/legal.txt) and the license | |
| # (docs/license.txt) that came with this distribution before using | |
| # this software. | |
| #------------------------------------------------------------------ | |
| # http://www.plainblack.com [email protected] | |
| #------------------------------------------------------------------ |
(a gist based on the old toolmantim article on setting up remote repos)
To collaborate in a distributed development process you’ll need to push code to remotely accessible repositories.
This is somewhat of a follow-up to the previous article setting up a new rails app with git.
Set up the new bare repo on the server:
| #!/usr/bin/env bash | |
| DST_PATH="${DST_PATH:-/tmp}" | |
| backup() { | |
| uuid="$1" | |
| label_name=$( xe vm-list uuid="$uuid" | grep 'name-label' | cut -b 24- ) | |
| snapshot_uuid=$( xe vm-snapshot vm="$uuid" new-name-label=backup_vm ) | |
| xe template-param-set is-a-template=false ha-always-run=false uuid="$snapshot_uuid" |
| ########## SETTINGS | |
| # On startup, lftp executes ~/.lftprc and ~/.lftp/rc. You can place aliases and 'set' commands | |
| # there. Some people prefer to see full protocol debug, use 'debug' to turn the debug on. | |
| # Certain commands and settings take a time interval parameter. It has the format Nx[Nx...], where N is time amount | |
| # (floating point) and x is time unit: d - days, h - hours, m - minutes, s - seconds. Default unit is second. E.g. | |
| # 5h30m or 5.5h. Also the interval can be 'infinity', 'inf', 'never', 'forever' - it means infinite interval. E.g. | |
| # 'sleep forever' or 'set dns:cache-expire never'. |
| #!/usr/bin/perl | |
| use strict; | |
| use Data::Dumper; | |
| use Getopt::Long; | |
| # author: Gavin Towey, 2008 [email protected] | |
| # todo, add "follow thread" capability | |
| # so we can give a process name or thread id & see | |
| # all activity in sequence for each thread |
| #!/usr/bin/perl -w | |
| use strict; | |
| use warnings; | |
| use POSIX; | |
| sub main { | |
| if(@ARGV < 3) { | |
| die "Usage: $0 pattern seconds output"; |
| changelog_from_deb () { | |
| # won't work when packages symlink their docs from another package from the same source; | |
| # you'll get "No changelog found." | |
| t="$(mktemp -d)" | |
| p="$(dpkg-deb -f "$1" Package)" | |
| fail=1 | |
| dpkg-deb --fsys-tarfile "$1" | \ | |
| tar -x --wildcards -C $t ./usr/share/doc/"$p"/changelog\* 2>/dev/null | |
| for f in changelog.Debian.gz changelog.gz; do |
| #!/usr/bin/env perl | |
| # | |
| # Fires HTTP request batches at the specified hostname | |
| # and analyzes the response times. | |
| # | |
| # If you have suspicious frequency of 3.00x, 9.00x, 21.00x | |
| # seconds, then most probably you have a problem of packet loss | |
| # in your network. | |
| # | |
| # [email protected], sometime in 2011 |
Kind of continue from the other gist how to install LAMP on an Amazon AMI
##Install git
sudo yum install git-core
##Create ssh directory since it doesn't exists by default on the Amazon AMI
I used to think that
ssh -X [email protected]
"just bloody worked". However this might not work - ssh must play ball on both sides of the link. On the remote (ssh server, X client) sshd must sit behind some port, tell Xlib to send X11 requests to it and then forward them back to you the X server (where the ssh client is). If the remote box is locked down to prevent this, you will get:
X11 forwarding request failed on channel 0
as part of an otherwise working login. As it happens, I am the admin of the remote box in question, so I followed the ArchWiki and went to /etc/ssh/sshd_config and uncommented