le1t0-deprec 2.1.6.001

data/THANKS

@@ -0,0 +1,17 @@
+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
+
+Seen on github http://github.com/mbailey/deprec/network
+
+isaac
+jasherai    Pritesh    		  (London)
+zippy       Eric Harris-Braun (NY) <eric@harris-braun.com>  http://eric.harris-braun.com
+kovacs      Michael Kovacs    (SF) <michael@mkovacs.com>    http://javathehutt.blogspot.com
+robc        Rob Caporetto     (Melbourne)  rcaporetto@gmail.com  http://www.rob-caporetto.com
+
+
+
+

data/bin/depify

@@ -0,0 +1,139 @@
+#!/usr/bin/env ruby
+
+require 'optparse'
+
+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)
+  #
+  # This loads all recipes minus the ones in rails.rb
+  # The recipes in rails.rb add 'before' and 'after' tasks to
+  # some of the builtin cap deploy tasks which are not appropriate
+  # for deploying a project that isn't setup to use deprec.
+  #
+  require 'deprec_minus_rails'
+
+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 'deprec'
+  
+    set :application, "set your application name here"
+    set :domain, "set domain name project will be served on here"
+    set :repository,  "git://github.com/\#{user}/\#{application}.git"
+    
+    # If you aren't using Subversion to manage your source code, specify
+    # your SCM below:
+    set :scm, :git
+   
+    set :ruby_vm_type,      :ree        # :ree, :mri
+    set :web_server_type,   :apache     # :apache, :nginx
+    set :app_server_type,   :passenger  # :passenger, :mongrel
+    set :db_server_type,    :mysql      # :mysql, :postgresql, :sqlite
+    
+    # set :packages_for_project, %w(libmagick9-dev imagemagick libfreeimage3) # list of packages to be installed
+    # set :gems_for_project, %w(rmagick mini_magick image_science) # 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, :no_release => true
+
+    # If you aren't deploying to /opt/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, "/opt/apps/\#{application}"
+    
+    namespace :deploy do
+      task :restart, :roles => :app, :except => { :no_release => true } do
+        top.deprec.app.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
+
+
+OptionParser.new do |opts|
+  opts.banner = "Usage: #{File.basename($0)} [path]"
+
+  opts.on("-c", "Install ~/.caprc file") do
+    create_file(File.join(ENV['HOME'], '.caprc'), caprc)
+    exit 0
+  end
+  
+  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 depify, 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 capify."
+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] depified!"

data/docs/EXAMPLE-installing_tracks.txt

@@ -0,0 +1,41 @@
+#
+# Install tracks locally
+#
+git clone git://github.com/bsag/tracks.git
+cd tracks
+
+cp config/database.yml.tmpl config/database.yml
+cp config/site.yml.tmpl config/site.yml
+cp -r log.tmpl log -u 
+rake db:create
+rake db:migrate
+./script/server  # Test locally
+
+
+#
+# Install deprec
+#
+sudo gem install deprec
+cap deprec:users:passwd HOSTS=192.168.0.135 USER=root # Change root password
+cap deprec:users:add 	HOSTS=192.168.0.135 USER=root # Add personal account
+
+
+#
+# Create deploy.rb file for tracks
+#
+depify .
+curl -o config/deploy.rb http://mbailey.github.com/deprec/deploy.rb-tracks
+# Edit config/deploy.rb specifying the domain name to serve the app on.	
+
+
+#
+# Install on remote server
+# 
+
+cap deprec:rails:install_stack
+cap deprec:db:install
+cap deploy:setup 
+cap deploy 
+cap deploy:migrate
+
+# Tracks is now running on your server. Enjoy!

data/docs/README.nagios

@@ -0,0 +1,22 @@
+deprec: Install and configure Nagios on Ubuntu 7.10 (gutsy), 8.04 (hardy)
+=========================================================================
+										 
+* Quickstart
+
+	# You need the following item defined in config/deploy.rb (or ~/.caprc)
+	role :nagios, 'monitor.blah.com'
+		
+	# Run the following on your workstation
+	export HOSTS=nagios.domain.name # replace with desired domain
+	cap deprec:apache:install
+	cap deprec:nagios:install
+	cap deprec:nagios_plugins:install
+	cap deprec:nagios:config_gen
+	cap deprec:nagios:htpass          # create web logins
+	cap deprec:nagios:config
+	cap deprec:apache:restart
+
+
+* The detail
+
+TBC

data/docs/README.rails

@@ -0,0 +1,17 @@
+deprec: Install Ruby on Rails app on fresh Ubuntu 7.10 (gutsy), 8.04 (hardy)
+============================================================================
+
+* Quickstart
+
+cd your_rails_app
+depify . 
+# Edit config/deploy.rb
+cap deprec:rails:install_stack
+
+# WARNING! Don't run the following command if you are using a shared 
+# database server that has already been installed.
+cap deprec:db:install 
+
+cap deploy:setup 
+cap deploy 
+cap deploy:migrate

data/docs/config_gen_explained.txt

@@ -0,0 +1,39 @@
+== 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 nginx
+
+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. 

data/docs/deprec-1.x/deprec-1.x.quickstart

@@ -0,0 +1,50 @@
+#
+# Old notes - YMMV
+#
+
+== deprec quickstart (with svn, trac and deployment to apache/mongrel/mysql)
+
+Here are instructions that will take a fresh install of Ubuntu Dapper (6.06.1 server), create a working rails app, create an SVN repository and trac installation for it and deploy it using apache, mongrel and mysql.
+
+All commands below are run on your local host. You will *never* be requested 
+to log into the remote server manually. Capistrano does all the work.
+
+- Mike
+
+# Install deprec on workstation
+sudo gem install deprec --include-dependencies
+echo 'require "deprec/recipes"'               >> ~/.caprc
+echo "ssh_options[:keys] = %w(${HOME}/.ssh/id_dsa)" >> ~/.caprc
+echo 'ssh_options[:paranoid] = false'         >> ~/.caprc
+echo 'ssh_options[:forward_agent] = true'     >> ~/.caprc
+
+# Create rails project on workstation and configure for deprec
+# (alternatively use an existing project)
+rails example
+cd example
+./script/generate scaffold_resource person name:string age:integer
+deprec --apply-to . --name example --domain www.example.com
+
+# NOTE! Use following two commands if you only have 'root' account on server
+# Some VPS services provide you with this when you sign up
+cap change_root_password_as_root # '_as_root' means run this as 'root' user
+cap setup_admin_account_as_root 
+
+# Copy your ssh keys to remote server to avoid having to type passwords
+cap setup_ssh_keys
+
+# Install all required software on remote server
+cap install_rails_stack svn_install trac_install
+
+# Import application into subversion respository and setup trac
+cap svn_setup
+cap trac_setup
+cap trac_user_add # this command allows you to create other trac users
+cap trac_start # trac is now available on http://www.example.com:9000/
+cap trac_stop  # if you had the need
+
+# Deploy application
+cap setup
+cap deploy_with_migrations
+cap apache_restart 
+# application is now running on http://www.example.com/people

data/docs/deprec-1.x/notes.txt

@@ -0,0 +1,12 @@
+# update timezone on gutsy
+# dpkg-reconfigure tzdata
+
+
+# Building Edge Capistrano
+You can build an edge gem by cd'ing to that directory and doing:
+
+1. svn info. Find the line that says "Revision:" and mark the revision number.
+2. rake PKG_BUILD=<rev> gem. Replace <rev> with the revision number.
+3. Look in the pkg subdirectory. Install that gem file via "gem install pkg/<gem file>"
+
+- Jamis

data/docs/windows_linux.txt

@@ -0,0 +1,350 @@
+http://cheat.errtheblog.com/s/deprec2/
+
+This is a copy of Chris Turners deprec2 howto (found here
+http://crackthenut.cracklabs.com/deprec2-your-slice/).  I'm adding it here
+because his site is down at the moment and I almost cried myself to sleep at the
+thought of losing it (thank you google cache)
+
+------------------------------
+
+This is a summary of how we build our servers and deploy our Rails apps from
+Ubuntu with the the current pre-release version of deprec2 + capistrano2.
+
+We use Slicehost to host our Rails apps (highly recommended) and we use deprec +
+capistrano to build our slices and deploy our apps. Mike Bailey has been hard at
+work on deprec2, which builds on capistrano2 by Jamis Buck. Thank you to Mike
+and Jamis for making these great tools that make life easier.
+
+The machine I was deploying from here (my “development” machine) is an
+Ubuntu Dapper slice with Ruby 1.8.6 and rubygems 1.0.1.
+
+The target machine here was a Slicehost slice with Ubuntu Gutsy.
+
+This will build the slice with Ruby 1.8.6 and latest rails (2.0.2 as of this
+writing) For serving up your app it installs mongrel+nginx (not apache - though
+it can easily be modified to use it)
+
+We use another remote machine to hold our source repositories and access those
+via the svn+ssh protocol. That is reflected in these instructions.
+
+Step 1 gets your development machine set up properly and is a one-time deal. You
+won’t have to repeat it for each new slice you build/deploy to.
+
+Step 2 installs everything you’ll need on your slice and deploys your app
+
+I wanted to get this posted sooner rather than later - it may be a bit terse -
+let me know if anything is confusing or inaccurate. I’ll TRY to keep these
+instruction updated as deprec2 moves into full release and other things change.
+Step 1 - Set Up The Machine You Are Deploying From (running Ubuntu in this case)
+
+This will make sure your development machine is set up the right way so that
+building your slice goes smoothly. You won’t have to repeat this when you
+build/deploy to future slices.
+1.1. Download the pre-release deprec2 gem
+
+Deprec 2.0 isn’t quite released yet, but there is a pre-release gem available.
+As of this writing it is at version 1.99-13. You can find it at deprec.org.
+
+The URL is almost guaranteed to change, but I’ve been grabbing the gem by:
+
+wget
+http://www.deprec.org/attachment/wiki/WikiStart/deprec-1.99.13.gem?format=raw -O
+deprec-1.99.13.gem
+
+1.2. Install Deprec
+
+sudo gem install deprec-1.99.13.gem
+
+Make sure you run this command from the same directory where you downloaded the
+deprec gem to.
+This will also install the latest version of capistrano, should you not already
+have it.
+1.3. Install fastthread
+
+sudo gem install fastthread
+
+Fastthread is necessary if you are using Ruby 1.8.6 to avoid possible deadlocks
+when using capistrano (or so I hear)
+1.4. Generate keys
+
+ssh-keygen -t rsa
+
+Accept the default name/location.
+
+Enter a passphrase if you wish.
+
+On my machine this creates my keys in /home/username/.ssh
+1.5. Setup a directory we can use for holding slice config files
+
+This directory is not specific to any one rails project and once we set it up we
+can use
+it in the future to do some of the initial setup for other slices we may build.
+
+From within /home/username:
+
+mkdir -p config_slices/config
+
+1.6. Create some files for Deprec/Capistrano
+
+Change to your config_slices directory and:
+
+depify .
+
+This creates:
+~/.caprc
+~/config_slices/Capfile
+~/config_slices/config/deploy.rb
+
+1.7. Edit your .caprc
+
+Open up ~/.caprc with a text editor
+
+Uncomment and update this line to point at the appropriate directory
+
+ssh_options[:keys] = %w(/path/to/your_home_dir/.ssh/id_rsa)
+
+like this on my machine:
+
+ssh_options[:keys] = %w(/home/username/.ssh/id_rsa)
+
+and uncomment these lines:
+
+ssh_options[:forward_agent] = ...
+ssh_options[:paranoid] = ...
+
+1.8. Generate some config files locally that will be pushed out to your slice in
+a future step
+
+Make sure you are still in config_slices directory
+
+cap deprec:ssh:config_gen
+
+This step generates configuration files which will be used to configure the ssh
+client and server on the slice.
+It also makes a directory to hold public keys for you and other users so deprec
+can find your keys and copy those out to the slice for you.
+1.9. (optional) Make some changes to the sshd_config before you send it to the
+slice
+
+This step changes a couple settings in the the file that will be used to
+configure the slice’s ssh server.
+It will be more secure if you don’t make either of these changes, but there is
+a chance you might find them to be useful.
+
+Edit ~/config_slices/config/ssh/etc/ssh/sshd_config
+
+If you still want to be able to ssh into your slice with a password (not only
+keys), change the line from
+
+PasswordAuthentication no
+
+to
+
+PasswordAuthentication yes
+
+If you still want to be able to ssh into your slice as root, change the line
+from
+
+PermitRootLogin no
+
+to
+
+PermitRootLogin yes
+
+1.10. Make some changes to the ssh_config before you send it to the slice
+
+This step changes a couple settings in the the file that will be used to
+configure the slice’s ssh client.
+This prevents the slice from getting a host key error when it uses ssh to check
+out your code from the svn repo.
+
+Edit ~/config_slices/config/ssh/etc/ssh/ssh_config
+
+Change:
+
+#StrictHostKeyChecking ask
+
+to
+
+StrictHostKeyChecking no
+
+1.11. Copy your public key to a place where deprec can find it
+
+cp ~/.ssh/id_rsa.pub ~/config_slices/config/ssh/authorized_keys/deploy_user
+
+Note: this copies and renames the file from id_rsa.pub to deploy_user
+
+You can put whatever you want for deploy_user - this will be the username we
+create on the slice later. I just use my last name. deprec makes it easy to
+add/manage additional users on the slice in the future - no need to have a
+single, dedicated “deploy” user.
+1.12. Copy your public key out to your svn machine
+
+PUT SOMETHING HERE
+
+Step 2 - Set up your slice and deploy your app
+
+Now that our development machine is set up we can move on to dealing with our
+slice.
+2.1. Create a new slice or rebuild one from SliceManager
+
+Note your slice’s IP address and new root password.
+2.2. Change the root password on the slice
+
+From within config_slices directory:
+
+cap deprec:users:passwd USER=root HOSTS=your.slice.ip.address
+
+   1. You will be prompted for which user to change the password for - default
+   is root, which is what we want - so just hit enter
+   2. You will be prompted for root’s new password - type one in
+   3. You will be prompted for the slice’s current root password - enter the
+   password slicehost emailed you
+
+Your slice’s root password has been changed.
+2.3. Create a new user on the slice to do your deployment with
+
+From within config_slices directory:
+
+cap deprec:users:add USER=root HOSTS=your.slice.ip.address
+
+   1. You will be prompted for a new username - enter whatever you used for
+   deploy_user in step 1.11
+   2. You will be asked if this should be an admin account -> enter yes
+   3. It should tell you it has found the key you copied above (if not you named
+   the key wrong or did not copy it to the correct place in 1.11) and ask if you
+   want to copy it out to the slice - default is yes - so hit enter
+   4. You will be prompted for a new password for deploy_user -> enter one
+   5. You will be prompted for a password - enter your slice’s new root
+   password from previous step
+
+Your deploy_user has now been created on the slice and that users public key has
+been copied over.
+2.4. (optional) Make sure your keys work and some stuff about ssh-agent
+
+At this point your user has been created on the slice and you should be able to
+ssh into the
+slice from your development machine.
+
+If you want to make sure your keys are working properly:
+
+PLACEHOLDER:
+
+-test ssh into your slice with no password
+
+-instruction for running ssh-agent to eliminate passphrases and make sure key
+can get forwarded to svn if applicable
+
+-also test you can also ssh into your svn (if you use svn+ssh) - if not then add
+public key to authorized_keys on svn machine
+2.5. Copy the ssh/sshd configs over to the slice
+
+From within config_slices directory:
+
+cap deprec:ssh:config USER=deploy_user HOSTS=my.slice.ip.address
+
+This configures the ssh client and server on the slice according to the config
+files we generated/edited in Step 1.
+2.6. Setup your deploy.rb
+
+cd my_rails_project
+depify .
+
+Edit my_rails_project/config/deploy.rb:
+
+If you do not keep database.yml under source control add this line at the top
+(after require ‘deprec’):
+
+set :database_yml_in_scm, false
+
+This will make sure that database.yml is symlinked from the shared/config dir
+(we’ll create that file later)
+If you keep database.yml in source control you should not put this line in.
+
+Now change the following lines to match your specifics:
+
+set :user, "deploy_user"
+set :application, "my_rails_project"
+set :repository, 
+"svn+ssh://my_svn_useruser@my_svn/path_to/my_rails_project/trunk"  #or whatever
+set :domain, "my.slice.ip.address" #or domain name if you have that setup
+role :app, domain
+role :web, domain
+role :db,  domain, :primary => true
+
+2.7. Install ruby/rails/mysql/mongrel/nginx and everything else you need on the
+slice
+
+From within my_rails_project directory:
+
+cap deprec:rails:install_rails_stack
+
+And you thought that would be hard…
+This step saves you a LOT of work (thank you Mike Bailey)
+It takes a little while, ~10 min when I ran it.
+2.8. Run the initial deploy to get things configured
+
+From within my_rails_project directory:
+
+cap deploy:setup
+cap deploy
+
+This sets up your application on the slice and does an initial check out from
+your svn.
+2.9. Create database.yml on the slice if you don’t keep it in source control
+
+Skip this step if database.yml is under source control.
+
+Add the following to my_rails_project/config/deploy.rb inside the
+namespace:deploy block
+
+db_params = {
+  "adapter"=>"mysql",
+  "database"=>"#{application}_#{rails_env}",
+  "username"=>"root",
+  "password"=>"",
+  "host"=>"localhost",
+  "socket"=>""
+}
+
+db_params.each do |param, default_val|
+  set "db_#{param}".to_sym,
+    lambda { Capistrano::CLI.ui.ask "Enter database #{param}" do |q|
+    q.default=default_val end}
+end
+
+task :my_generate_database_yml, :roles => :app do
+  database_configuration = "#{rails_env}:\n"
+  db_params.each do |param, default_val|
+    val=self.send("db_#{param}")
+    database_configuration<<"  #{param}: #{val}\n"
+  end
+  run "mkdir -p #{deploy_to}/#{shared_dir}/config"
+  put database_configuration, "#{deploy_to}/#{shared_dir}/config/database.yml"
+end
+
+Now run this task to create database.yml
+
+cap deploy:my_generate_database_yml
+
+Follow the prompts - this makes database.yml - the defaults are likely ok (just
+hit enter) at all of the prompts.
+
+2.10. Create the database and apply migrations
+
+Still from within my_rails_project directory:
+
+cap deprec:db:create
+cap deprec:db:migrate
+
+This creates your database and applies your migrations.
+
+2.11. Restart mongrel+nginx
+
+Still from within my_rails_project directory:
+
+cap deprec:mongrel:restart
+cap deprec:nginx:restart
+
+Now you should be able to point your browser at your slice and see your app
+running. Congrats!