ClusterSSH is a tool for making the same change on multiple servers at the same time. The ‘cssh’ command opens an administration console and an xterm to all specified hosts. Any text typed into the administration console is replicated to all windows. All windows may also be typed into directly. This tool is intended for (but not limited to) cluster administration where the same configuration or commands must be run on each node within the cluster. Performing these commands all at once via this tool ensures all nodes are kept in sync.
Shelr is a service which allows you to record and replay and publish your terminal on http://shelr.tv. This can be useful when you need to provide instruction on how a task was accomplished to a client. Granted, you will not want to publish any sensitive info when using this tool. The code for Shelr.tv service is also available on github. Continue reading “Shelr”
BetterLinux is a collection of system resource management and monitoring tools intended for hosting providers, data centers, SaaS companies, and cloud environments. With it, you can control use and allocation of CPU, memory, MySQL, device I/O bandwidth, and IP bandwidth resources. Individual users and processes that exceed set resource limits can be isolated from other system users and throttled as necessary. Continue reading “BetterLinux – A CloudLinux Alternative”
If working in the Terminal gets a little confusing because you run so many commands at once, this little trick will put a separator in between each prompt so you can easily see the last few commands you ran. Blogger Emilis found that his bash prompt was getting a bit too cluttered, so he implemented this tweak to throw a long, dotted line between each command. He also bolded each command he ran, so he could easily scroll back and tell the difference between each command he ran and its output. Continue reading “Add a Separator Between Commands in Linux Terminal”
spf13-vim is a distribution of vim plugins and resources for Vim, GVim and MacVim. It is a completely cross platform distribution that stays true to the feel of vim while providing modern features like a plugin management system, autocomplete, tags and tons more.
Easy Installation *nix and os x The easiest way to install spf13-vim is to use our automatic installer by simply copying and pasting the following line into a terminal. This will install spf13-vim and backup your existing vim configuration. If you are upgrading from a prior version (before 3.0) this is also the recommended installation. curl http://j.mp/spf13-vim3 -L -o - | sh
Updating to the latest version $HOME/to/spf13-vim/ git pull vim +BundleInstall! +BundleClean +q
You can use Google Docs to monitor your website’s uptime and get instant alerts if your site is down or unavailable to visitors. The latest version of this Google Docs based website monitoring tool is even better:
You can now monitor multiple websites and blogs for downtime/uptime in one go.
In addition to email alerts, you can now choose to receive SMS alerts on our phone if any of your sites are down.
The text alerts are routed through Google Calendar and are therefore free.
In fact, this is probably the only tool that lets you monitor unlimited number of website domains and offers both SMS and email based alerts without charging a penny. Here’s how you can install the monitor in Google Docs in less than 60 seconds:
Build your own website monitoring tool with Google Docs, SMS alerts included
Real-time Website Monitor with Text Alerts
Click here to create a personal copy of the Website Monitor HD sheet in your own Google Docs account.
You’ll see a new Website Monitor menu in the toolbar. Click Initialize and you’ll get a pop-up asking for authorization. Just say Yes.
Put your Website URLs in cell B2 (comma separated) and your email address in cell B3.
Go to the Website Monitor menu again and choose “Start Monitoring”.
That’s it. Close the Google Docs sheet and it will monitor your sites in the background. If you do not wish to receive SMS alerts, simply change the value of cell B4 from Yes to No.
The full source code of the project is available at ctrlq.org – no one else has access to your data and you can disable the script anytime by setting the email address in cell B3 to blank.
A feature request for tarbackup is using a private ssh key instead of a password to connect to the tarbackup server when using sftp to backup files. I’m happy to report that we now support public/private keys for sftp authentication!
To use an ssh key with tarbackup, first use this command to create your public/private key-pair: # mkdir ~/.ssh # cd ~/.ssh # ssh-keygen -f tarbackup_rsa -C .youremail. -N . -t rsa -q
This will generate 2 files: tarbackup_rsa and tarbackup_rsa.pub. tarbackup_rsa is your private ssh key, you will keep this on your computer as proof that you are who you are. tarbackup_rsa.pub is a public key that you send to the server so that tarbackup.com can authenticate you when you log in via sftp in the future.
To use your private key to authenticate you when you login via sftp, you need to create an ssh_config file in your home directory with: # echo "IdentityFile ~/.ssh/tarbackup_rsa" > ~/ssh_config
This is the config file that specifies where your private ssh key is.
You’ll pass the ssh_config file as a parameter to the sftp program when you connect to tarbackup.com via sftp: # sftp -F ~/ssh_config email@example.com
And that’s it! Let me know if you have any feedback or questions@davidnanch.