1
0
Fork 0
mirror of https://github.com/capistrano/capistrano synced 2023-03-27 23:21:18 -04:00

Replace ``` with {% prism ruby %}

Sorry, didn't notice you are using jekyll-prism! :)
This commit is contained in:
Huiming Teo 2013-07-15 16:17:52 +08:00
parent a49da4bac4
commit ae167def14

View file

@ -10,7 +10,7 @@ Capistrano v3 provides a default **deploy flow** and a **rollback flow**:
When you run `cap production deploy`, it invokes the following tasks in When you run `cap production deploy`, it invokes the following tasks in
sequence: sequence:
``` {% prism ruby %}
deploy:starting - start a deployment, make sure everything is ready deploy:starting - start a deployment, make sure everything is ready
deploy:started - started hook (for custom tasks) deploy:started - started hook (for custom tasks)
deploy:updating - update server(s) with a new release deploy:updating - update server(s) with a new release
@ -19,7 +19,7 @@ deploy:publishing - publish the new release
deploy:published - published hook deploy:published - published hook
deploy:finishing - finish the deployment, clean up everything deploy:finishing - finish the deployment, clean up everything
deploy:finished - finished hook deploy:finished - finished hook
``` {% endprism %}
Notice there are several hook tasks e.g. `:started`, `:updated` for Notice there are several hook tasks e.g. `:started`, `:updated` for
you to hook up custom tasks into the flow using `after()` and `before()`. you to hook up custom tasks into the flow using `after()` and `before()`.
@ -29,7 +29,7 @@ you to hook up custom tasks into the flow using `after()` and `before()`.
When you run `cap production deploy:rollback`, it invokes the following When you run `cap production deploy:rollback`, it invokes the following
tasks in sequence: tasks in sequence:
``` {% prism ruby %}
deploy:starting deploy:starting
deploy:started deploy:started
deploy:reverting - revert server(s) to previous release deploy:reverting - revert server(s) to previous release
@ -38,7 +38,7 @@ deploy:publishing
deploy:published deploy:published
deploy:finishing_rollback - finish the rollback, clean up everything deploy:finishing_rollback - finish the rollback, clean up everything
deploy:finished deploy:finished
``` {% endprism %}
As you can see, rollback flow shares many tasks with deploy flow. But note that, rollback flow runs its own `:finishing_rollback` task because its As you can see, rollback flow shares many tasks with deploy flow. But note that, rollback flow runs its own `:finishing_rollback` task because its
cleanup process is usually different from deploy flow. cleanup process is usually different from deploy flow.
@ -47,18 +47,18 @@ cleanup process is usually different from deploy flow.
Assume you require the following files in `Capfile`, Assume you require the following files in `Capfile`,
``` {% prism ruby %}
# Capfile # Capfile
require 'capistrano/setup' require 'capistrano/setup'
require 'capistrano/deploy' require 'capistrano/deploy'
require 'capistrano/bundler' require 'capistrano/bundler'
require 'capistrano/rails/migrations' require 'capistrano/rails/migrations'
require 'capistrano/rails/assets' require 'capistrano/rails/assets'
``` {% endprism %}
When you run `cap production deploy`, it runs this following tasks: When you run `cap production deploy`, it runs this following tasks:
``` {% prism ruby %}
deploy deploy
deploy:starting deploy:starting
[before] [before]
@ -84,11 +84,11 @@ deploy
deploy:cleanup deploy:cleanup
deploy:finished deploy:finished
deploy:log_revision deploy:log_revision
``` {% endprism %}
For `cap production deploy:rollback`, it runs these tasks: For `cap production deploy:rollback`, it runs these tasks:
``` {% prism ruby %}
deploy deploy
deploy:starting deploy:starting
[before] [before]
@ -108,4 +108,5 @@ deploy
deploy:cleanup_rollback deploy:cleanup_rollback
deploy:finished deploy:finished
deploy:log_revision deploy:log_revision
``` {% endprism %}