Deploying Rails Apps, Part 6: Writing Capistrano Tasks - Vladi Gleba - 0 views
-
we can write our own tasks to help us automate various things.
-
organizing all of the tasks here under a namespace
-
upload a file from our local computer.
- ...27 more annotations...
-
learn about is SSHKit and the various methods it provides
-
SSHKit was actually developed and released with Capistrano 3, and it’s basically a lower-level tool that provides methods for connecting and interacting with remote servers
-
on(): specifies the server to run on
-
within(): specifies the directory path to run in
-
with(): specifies the environment variables to run with
-
run on the application server
-
within the path specified
-
with certain environment variables set
-
execute(): the workhorse that runs the commands on your server
-
upload(): uploads a file from your local computer to your remote server
-
capture(): executes a command and returns its output as a string
-
-
upload() has the bang symbol (!) because that’s how it’s defined in SSHKit, and it’s just a convention letting us know that the method will block until it finishes.
-
But in order to ensure rake runs with the proper environment variables set, we have to use rake as a symbol and pass db:seed as a string
-
This format will also be necessary whenever you’re running any other Rails-specific commands that rely on certain environment variables being set
-
I recommend you take a look at SSHKit’s example page to learn more
-
make sure we pushed all our local changes to the remote master branch
-
run this task before Capistrano runs its own deploy task
-
actually creates three separate tasks
-
I created a namespace called deploy to contain these tasks since that’s what they’re related to.
-
we’re using the callbacks inside a namespace to make sure Capistrano knows which tasks the callbacks are referencing.
-
custom recipe (a Capistrano term meaning a series of tasks)
-
/shared: holds files and directories that persist throughout deploys
-
When you run cap production deploy, you’re actually calling a Capistrano task called deploy, which then sequentially invokes other tasks
-
your favorite browser (I hope it’s not Internet Explorer)
-
Deployment is hard and takes a while to sink in.
-
the most important thing is to not get discouraged
-
I didn’t want other people going through the same thing