Permalink
Browse files

Clean up generated README

Reference thoughtbot/dotfiles rather than try to keep its
documentation up to date here.
  • Loading branch information...
1 parent 61c3950 commit 7d8d89b597e4363e654ff91114c660925cde548b @croaky croaky committed Aug 7, 2012
@@ -167,12 +167,6 @@ def create_heroku_apps
run "#{path_addition} heroku create #{app_name}-staging --remote=staging"
end
- def document_heroku
- heroku_readme_path = find_in_source_paths 'HEROKU_README.md'
- documentation = File.open(heroku_readme_path).read
- inject_into_file('README.md', "#{documentation}\n", :before => 'Most importantly')
- end
-
def create_github_repo(repo_name)
path_addition = override_path_for_tests
run "#{path_addition} hub create #{repo_name}"
@@ -143,7 +143,6 @@ def create_heroku_apps
if options[:heroku]
say 'Creating Heroku apps'
build :create_heroku_apps
- build :document_heroku
end
end
View
@@ -1,66 +0,0 @@
-Staging and production environments
------------------------------------
-
-We're using Heroku as a hosting provider. Deploying to Heroku is done via git. So, set up your git remotes for each environment:
-
- git remote add staging git@heroku.com:your-app-staging.git
- git remote add production git@heroku.com:your-app-production.git
-
-Heroku
-------
-
-The following are mostly aliases from the `dotfiles` script.
-
-To access your code on Heroku:
-
- staging
- production
-
-That will drop you into a Rails console for either environment. You can run ActiveRecord queries from there.
-
-To dump staging or production data into your development environment:
-
- db-pull-staging
- db-pull-production
-
-You will see progress bars for each db index and table.
-
-We can create a database backup at any time:
-
- db-backup-production
-
-View backups:
-
- db-backups
-
-To destroy a backup:
-
- heroku pgbackups:destroy b003 --remote production
-
-Transfer production data to staging:
-
- db-copy-production-to-staging
-
-More information in the [Dev Center](http://devcenter.heroku.com/articles/pgbackups).
-
-To check the status of running app servers, background jobs, cron jobs, etc:
-
- staging-process
- production-process
-
-To see the performance of the staging application, see:
-
- https://heroku.newrelic.com/...
-
-To see the performance of the production application, see:
-
- https://heroku.newrelic.com/...
-
-ENV variables
--------------
-
-ENV variables like AWS keys should not be in the source code. They are configuration and should be stored as ENV variables. On Heroku, they are called "config variables." You can pull config variables using the `heroku-config` plugin that comes with the `laptop` script:
-
- heroku config:pull --remote staging
-
-You'll see the Amazon credentials as config vars. You should delete lines that don't apply, like Redis to Go connection strings.
View
@@ -173,6 +173,10 @@ Watch logs and metrics dashboards. If the feature is working, merge into master.
git merge production --ff-only
git push origin master
+Use scripts from [thoughtbot/dotfiles](http://github.com/thoughtbot/dotfiles)
+to quickly access the Heroku console, backup the production database, and
+transfer production data to staging.
+
Formatting
----------

0 comments on commit 7d8d89b

Please sign in to comment.