centostrano 0.1

data/README

@@ -0,0 +1,166 @@
+------------------------------------------
+Centostrano - port of deprec2 to CentOS
+------------------------------------------
+
+This project aims to port deprec 2 to CentOS. Intention is to keep Centostrano
+as close to original deprec 2 as possible, but some changes are implemented, 
+because of conflicts between Centostrano and deprec 2. Instead of binary 
+'depify' one must use 'centify', instead of 'deprec' namespace of capistrano 
+tasks one must use 'centos', everything else should be the same as 
+original deprec, so original deprec info files are included too.
+
+Currently Centostrano supports CentOS 5.1 and 5.2.
+
+Gitosis and PostgreSQL installation and setup scripts are added
+
+Any feedback is welcome!
+
+== Credits
+
+Saulius Grigaitis: porter and maintainer of Centostrano
+Mike Bailey: Original creator of deprec 2
+
+== Links
+
+Centostrano homepage: http://rubyonrails.lt/redmine/projects/show/centostrano
+Centostrano at github: http://www.rubyonrails.lt/centostrano
+Centostrano at rubyforge: http://rubyforge.org/projects/centostrano/
+
+== Original deprec 2 README
+
+------------------------------------------
+deprec - Deployment Recipes for Capistrano
+------------------------------------------
+
+== Introduction
+
+The deprec [1] gem is a set of tasks for Capistrano [2]. These tasks provide
+for the installation, configuration and control of system services. Deprec 
+was created in 2006 by Mike Bailey to setup an environment for running Ruby 
+on Rails web applications on Ubuntu dapper servers. Since then its uses have
+grown to installing mail, monitoring, high availability IP failover and other 
+services.
+
+The tasks are run at the command line on your workstation and connect to 
+remote servers via ssh to run commands and copy out files.
+
+Deprec-2.x is a complete rewrite of the project that achieves the following:
+
+- support for Capistrano 2
+- support for more services (heartbeat, nagios, nginx, ntp, postfix, etc) 
+- creation of a standard base set of task names
+- tasks are cleanly separated into namespaced units (one file per service)
+- service config files are stored locally to enable edits and version control
+- interactive prompting for missing config values
+
+One idea that is in the trash can is supporting other distros/OS's. While I got
+caught up in the excitement of The Big Rewrite I've decided I don't need it. If 
+you want to deploy to something other than Ubuntu I suggest you look for other 
+alternatives.
+
+Deprec and Capistrano are written in the Ruby programming language [3] however 
+no knowledge of Ruby is required to use it. Users should be able to write 
+new tasks and modify existing options without prior knowledge of Ruby.
+
+
+== Installation
+
+Deprec can be obtained from rubyforge[4] and installed using rubygems[5].
+
+	sudo gem install deprec  # installs deprec and dependancies 
+	cap depify .			 # creates ~/.caprc which you may edit
+	cap -T					 # should list lots of deprec tasks
+
+The .caprc file is loaded every time you use Capistrano. It in turn loads 
+the deprec tasks so you always have them available. Editing the .caprc file 
+in your home directory allows you to specify the location of your ssh key
+and enable some other useful options (documented in the comments). You can
+also put tasks here that you want to always have access to.
+
+
+== Getting a Ruby on Rails app running on a fresh Ubuntu server
+
+This is still what brings people to deprec. You can install a full Rails stack
+and get multiple apps running on it in much less time than it would take to 
+do it manually. Think an hour vs. a weekend. (The irony is I'm up writing this
+on a Saturday night.)
+
+	export HOSTS=<target.host.name>
+
+	# Install Rails stack
+	cap deprec:rails:install_rails_stack
+
+	# Install mysql (if it's running on the same box)
+	cap deprec:mysql:install
+	cap deprec:mysql:config_gen
+	cap deprec:mysql:config
+
+	# Install your Rails app
+	cap deploy:setup
+	cap deploy
+	cap deprec:db:create
+	cap deprec:db:migrate
+	cap deprec:nginx:restart
+	cap deprec:mongrel:restart
+
+You can find documentation on the deprec site. http://www.deprec.org/
+
+
+== Installing other things
+
+I plan to document other things I use deprec for on http://www.deprec.org/. 
+Feel free to poke around and see what's there. I use deprec to provision and 
+manage servers so you might find some things in there I haven't documented. Lucky you.
+
+
+== Disclaimer
+
+The tasks run commands that may make changes to your workstation and remote server. 
+You are advised to read the source and use at your own risk.
+
+
+== Credits
+
+Deprec is written and maintained by Mike Bailey <mike@bailey.net.au>. 
+More about me here: [http://mike.bailey.net.au/]
+
+Deprec was inspired and uses the brilliantly executed Capistrano. Thanks Jamis!
+This gem includes a modified copy of Neil Wilson's very useful vmbuilder_plugins gem.
+
+
+== Thanks
+
+Eric Harris-Braun: great testing, bug reports and suggestions
+Gus Gollings: helped restore www.deprec.org
+Craig Ambrose: testing, documentation and beer
+
+
+== License
+
+Deprec is licenced under the GPL. This means that you can use it in commercial 
+or open source applications. More details found here:
+http://www.gnu.org/licenses/gpl.html
+
+deprec - deployment recipes for capistrano
+Copyright (C) 2006-2008 Mike Bailey
+
+This program is free software; you can redistribute it and/or
+modify it under the terms of the GNU General Public License
+as published by the Free Software Foundation; either version 2
+of the License, or (at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program; if not, write to the Free Software
+Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, USA.
+
+
+[1] http://www.deprec.org
+[2] http://www.capify.org
+[3] http://www.ruby-lang.org/en/
+[4] http://rubyforge.org/
+[5] http://rubygems.org/

data/THANKS

@@ -0,0 +1,5 @@
+Big thanks go to the following people. Apologies to any I have missed! - Mike
+
+20080226 Chris Turner for an excellent HOWTO http://crackthenut.cracklabs.com/deprec2-your-slice-from-windows/
+20080206 Eric Harris-Braun for some great testing, bug reports and suggestions.
+20071004 Gus Gollings for helping restore www.deprec.org

data/bin/centify

@@ -0,0 +1,137 @@
+#!/usr/bin/env ruby
+
+require 'optparse'
+
+OptionParser.new do |opts|
+  opts.banner = "Usage: #{File.basename($0)} [path]"
+
+  opts.on("-h", "--help", "Displays this help info") do
+    puts opts
+    exit 0
+  end
+
+  begin
+    opts.parse!(ARGV)
+  rescue OptionParser::ParseError => e
+    warn e.message
+    puts opts
+    exit 1
+  end
+end
+
+if ARGV.empty?
+  abort "Please specify the directory to centify, e.g. `#{File.basename($0)} .'"
+elsif !File.exists?(ARGV.first)
+  abort "`#{ARGV.first}' does not exist."
+elsif !File.directory?(ARGV.first)
+  abort "`#{ARGV.first}' is not a directory."
+elsif ARGV.length > 1
+  abort "Too many arguments; please specify only the directory to centify."
+end
+
+def unindent(string)
+  indentation = string[/\A\s*/]
+  string.strip.gsub(/^#{indentation}/, "")
+end
+
+
+caprc = unindent(<<-FILE)
+  # .caprc - Capistrano configs (added by deprec gem [www.deprec.org])
+  #
+  # Include settings that you want active whenever you use Capistrano
+  # You can over ride these for particular projects by putting entries
+  # into Capfile or deploy.rb for those projects
+  #
+  # Uncomment any of the following entries to enable them.
+  #
+  # Include deprec - deployment recipes for Capistrano (www.deprec.org)
+  #
+  # require 'deprec'
+  #
+  require 'centostrano'
+  #
+  # SSH options
+  #
+  # Use ssh keys instead of typing password every time
+  # Replace with the path to your ssh public key
+  # ssh_options[:keys] = %w(/path/to/your_home_dir/.ssh/id_rsa)
+  #
+  # Allow ssh keys to be forwarded (to scm server, through :gateway, etc) 
+  # ssh_options[:forward_agent] = true 
+  #
+  # Stop some annoying warnings
+  # ssh_options[:paranoid] = false
+FILE
+
+files = {
+  "Capfile" => unindent(<<-FILE),
+    load 'deploy' if respond_to?(:namespace) # cap2 differentiator
+    Dir['vendor/plugins/*/recipes/*.rb'].each { |plugin| load(plugin) }
+    Dir['config/*/recipes.rb'].each { |plugin| load(plugin) }
+    load 'config/deploy'
+  FILE
+
+  "config/deploy.rb" => unindent(<<-FILE),
+    require 'centostrano'
+  
+    set :application, "set your application name here"
+    set :domain, "set domain name project will be served on here"
+    set :repository,  "git@\#{domain}:\#{application}.git"
+    # set :gems_for_project, %w(dr_nic_magic_models swiftiply) # list of gems to be installed
+    
+    # Update these if you're not running everything on one host.
+    role :app, domain
+    role :web, domain
+    role :db,  domain, :primary => true
+    role :scm, domain # used by deprec if you want to install subversion
+    
+    default_run_options[:pty] = true 
+
+    # If you aren't deploying to /var/www/apps/\#{application} on the target
+    # servers (which is the deprec default), you can specify the actual location
+    # via the :deploy_to variable:
+    # set :deploy_to, "/var/www/\#{application}"
+
+    # If you aren't using Subversion to manage your source code, specify
+    # your SCM below:
+    set :scm, :git
+    
+    namespace :deploy do
+      task :restart, :roles => :app, :except => { :no_release => true } do
+        top.centos.mongrel.restart
+      end
+    end
+    
+  FILE
+}
+
+def create_file(file, content)
+  if !File.exists?(File.dirname(file))
+    puts "[add] creating directory `#{File.dirname(file)}'"
+    Dir.mkdir(File.dirname(file))
+  end
+  if File.exists?(file)
+    warn "[skip] `#{file}' already exists"
+  elsif File.exists?(file.downcase)
+    warn "[skip] `#{file.downcase}' exists, which could conflict with `#{file}'"
+  else
+    puts "[add] writing `#{file}'"
+    File.open(file, "w") { |f| f.write(content) }
+  end
+end
+
+create_file(File.join(ENV['HOME'], '.caprc'), caprc)
+
+base = ARGV.shift
+config_dir = File.join(base,'config')
+if File.directory?(config_dir)
+  files.each do |file, content|
+    create_file(File.join(base, file), content)
+  end
+else
+  warn "[warn] directory `#{config_dir}' does not exist"
+  warn "[skip] '#{base}/Capfile'"
+  warn "[skip] '#{base}/config/deploy.rb'"
+end
+
+puts "[done] centified!"

data/docs/ANNOUNCE.deprec2

@@ -0,0 +1,47 @@
+== Configuration
+
+deprec2 has a two stage process for generating/deploying configuration files.
+Configuration files for web, app, db servers (and more) are generated from 
+templates and put under the config/ tree in your Rails apps source tree. 
+Alternatively you could create a non-rails-app tree to hold them. The second 
+stage is pushing the files out to the destination servers. This used to be a 
+one stage process in deprec1 however the change has been made so that:
+
+- all config files for a project can be kept under source control
+- you can make changes to config files that are not available through deprec
+
+Many of the settings in these config files are based on values in the projects 
+deploy.rb file. Others reflect defaults in deprec that you can override by adding 
+fields to deploy.rb. This means you may never need to edit the generated config 
+files directly. You can generate a set of config files with the following:
+
+	cap deprec:nginx:config_gen # generates config files for trac from templates
+	
+config_gen is re-runnable and will prompt you before overwriting a file. It will
+also show you what changes overwriting would make (in diff format) to help you
+decide whether you want it to do so.
+
+Changes to service configuration should never be made on the server. Deprec 
+acknowledges this by offering no assistance to people who want to copy config 
+files back from servers. But pushing the files out couldn't be simpler!
+
+	cap deprec:nginx:config # pushes out all config files for trac
+
+deprec2 takes into consideration the fact that that some services are used to 
+host more than one application. For example, a webserver will often have one 
+main configuration and a number of virtual host configurations. Monit has a
+single config file (/etc/monitrc) but will also load other configs it finds in
+a certain directory (/etc/monit.d).
+
+When you deploy a Ruby on Rails app with deprec it drops configs for your project
+into the config/ directory for your project and symlinks them into a shared path
+on the server. This means you can install multiple apps on a remote server and 
+they shouldn't stop on each other. 
+	
+== Extra services
+
+- nginx
+- monit
+- postfix
+- nagios
+- more...

data/docs/README.install

@@ -0,0 +1,88 @@
+== Installation and initial setup for deprec2
+
+Install deprec with the following command (requires ruby and rubygems installed)
+
+	sudo gem install deprec
+
+Let's create a directory to manage all our host config details 
+This supports as many hosts as you need to manage and will be the dir
+you run your deprec commands from when managing the servers. Note that
+you don't need to do this if you just want to deploy a single Ruby on 
+Rails application. In this case the config/ dir in your project can
+serve the same purpose. For those who aren't interested in Ruby on Rails
+or want to use deprec for more than just deploying one rails app, the 
+following may come in handy.
+
+	mkdir -p sys/config		  # change 'sys' to whatever you want
+	cd sys					  # 
+	depify .				  # create Capfile and config/deploy.rb
+	cap deprec:ssh:config_gen # generates ssh server configs
+
+If you have an authorized_keys file, copy it to a location where deprec
+can find it. Deprec will then offer to copy it out to remote hosts when
+you setup new accounts for yourself. If you don't have authorized_keys,
+copy out your id_rsa.pub or id_dsa.pub.
+
+You can also put the authorized_keys of colleagues in this dir and deprec
+will offer to copy them out when creating accounts for them too.
+
+We name these files using the username of their owner.
+
+	cp ~/.ssh/authorized_keys config/ssh/authorized_keys/${USER}
+
+Define an environment variable for the server we'll be working on
+
+	export HOSTS=<your.slice.address>
+
+Change the root password you received for your new slice.
+
+	cap deprec:users:passwd USER=root
+
+		Enter user to change password for  |root|
+		Password: 
+		Enter new UNIX password: 
+		Retype new UNIX password: 
+
+
+Create an account with sudo access for mysql^H^Hself
+
+	cap deprec:users:add USER=root 
+
+		Enter userid for new user  |root|
+		mbailey
+		Should this be an admin account?  |no|
+		yes
+		I've found an authorized_keys file for mbailey. Should I copy it out?  |yes|
+		Password: 
+		Setting pasword for new account
+		Enter new UNIX password: 
+		Retype new UNIX password: 
+
+
+Create another account without sudo access for a colleague.
+Notice how I longer need to specify USER=root? That's because I'm using the 
+account I just created.
+
+	cap deprec:users:add
+
+		Enter userid for new user  |mbailey|
+		ben
+		Should this be an admin account?  |no|
+		Password: 
+		Setting pasword for new account
+		Enter new UNIX password: 
+		Retype new UNIX password: 
+ 
+I prefer to disallow ssh password based login for security reasons. I also 
+turn off DNS lookups by sshd as they are often responsible for a 2 second 
+lag on login. Be warned that turning off ssh passwords will prevent someone 
+without an ssh key setup from logging in so use this with caution. Deprec 
+makes it painless to upload their key when you create their account though 
+so you've got no excuse to leave passwords turned on.
+
+You can upload the ssh configs currently residing in config/ssh/etc/ssh by 
+running this:
+
+	cap deprec:ssh:config
+
+You can now continue to the other READMEs