Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Proper formatting of code example in the Namespacing Tasks section. #7

Merged
merged 1 commit into from Aug 2, 2011
Jump to file or symbol
Failed to load files and symbols.
+8 −8
Split
View
@@ -120,17 +120,17 @@ It stands to reason that with such a wide scope of available uses, there would b
Defining a task in this way, and more about how the task blocks are arranged is forthcoming; however imagine we had two tasks `backup` perhaps, that needed to work differently on different roles.. here's how namepsaces solve that problem
- namespace :web_server do
- task :backup do
- puts "In Example Backup Web-Server"
+ namespace :web_server do
+ task :backup do
+ puts "In Example Backup Web-Server"
+ end
end
- end
- namespace :database_server do
- task :backup do
- puts "In Example Backup Database-Server"
+ namespace :database_server do
+ task :backup do
+ puts "In Example Backup Database-Server"
+ end
end
- end
Whilst the tasks in the first example might be listed by `cap -T` as: