From 9c4ede25614277db2e960ad23e7b5b925bfbd43d Mon Sep 17 00:00:00 2001 From: Thomas Kriechbaumer Date: Thu, 22 Jan 2015 15:23:09 +0000 Subject: [PATCH] fix external links --- .../2013-06-01-release-announcement.markdown | 5 +---- .../getting-started/cold-start/index.markdown | 20 ++++++++----------- .../installation/index.markdown | 2 +- 3 files changed, 10 insertions(+), 17 deletions(-) diff --git a/_posts/2013-06-01-release-announcement.markdown b/_posts/2013-06-01-release-announcement.markdown index c4a14a5d..4aae5058 100644 --- a/_posts/2013-06-01-release-announcement.markdown +++ b/_posts/2013-06-01-release-announcement.markdown @@ -103,10 +103,7 @@ essentially a dependency resolution system, it offers a lot of nice ways to, for example build a tarball as a dependency of uploading it and deploying it. This has allowed us to do away with the *copy* strategy all together, as it -can now be implemented from scratch in fewer than ten lines of code. You can -check out the [replicating the copy -strategy](/screencasts/replicating_the_copy_strategy) screencast and -acompanying documentation if you want to explore that any further. +can now be implemented from scratch in fewer than ten lines of code. The guiding principle is dependency resolution, and interoperability with other tools, for example: diff --git a/documentation/getting-started/cold-start/index.markdown b/documentation/getting-started/cold-start/index.markdown index 3f5a730a..bc499ddb 100644 --- a/documentation/getting-started/cold-start/index.markdown +++ b/documentation/getting-started/cold-start/index.markdown @@ -102,14 +102,12 @@ simply call: me@localhost $ cap staging git:check {% endhighlight %} -This task is defined -[here](https://github.com/capistrano/capistrano/blob/master/lib/capistrano/tasks/git.rake) -in the source code, and looks a lot like what we wrote above to check the file -permissions, however the Git check recipe is a bit more complicated, having to -potentially deal with three different authentication schemes, which need to be -worked around differently. This task expresses a *dependency* on the -`git:git-wrapper` task which is resolved first for us by Capistrano. (This is -one of the pieces we inherit from Rake) +This task is defined in the default Git SCM-strategy and looks a lot like what +we wrote above to check the file permissions, however the Git check recipe is +a bit more complicated, having to potentially deal with three different +authentication schemes, which need to be worked around differently. This task +expresses a *dependency* on the `git:git-wrapper` task which is resolved first +for us by Capistrano. (This is one of the pieces we inherit from Rake) If this fails we'll see: @@ -145,10 +143,8 @@ To run through that shortly, what did we do: 2. Capistrano recognised that in order to fulfil this request, it had to first execute the task `git:wrapper`, a *prerequisite*. 3. Capistrano executed the `git:wrapper` task, and uploaded the - `/tmp/git-ssh.sh` file, and made it executable. This satisfies the - `git:wrapper` task defined - [here](https://github.com/capistrano/capistrano/blob/v3/lib/capistrano/tasks/git.rake#L9) - in the source code. This script is actually processed as a template. + `/tmp/git-ssh.sh` file, and made it executable. + This script is actually processed as a template. 4. With the git wrapper in place, we can safely script against Git without it prompting us for input, so we ask git to `ls-remote` on the repository we defined. As this exited with an [unclean diff --git a/documentation/getting-started/installation/index.markdown b/documentation/getting-started/installation/index.markdown index c469b46a..1efdf05d 100644 --- a/documentation/getting-started/installation/index.markdown +++ b/documentation/getting-started/installation/index.markdown @@ -76,7 +76,7 @@ the risk of accidentally upgrading to `v3`. -- [rubygems]: http://rubygems.org/ -[rubygems-pessimistic-operator]: http://docs.rubygems.org/read/chapter/16#page74 +[rubygems-pessimistic-operator]: http://guides.rubygems.org/patterns/#pessimistic-version-constraint [capistrano-rails-asset-pipeline-readme]: https://github.com/capistrano/rails/blob/master/README.md [capistrano-rails-database-migrations-readme]: https://github.com/capistrano/rails/blob/master/README.md [capistrano-rails-gem-bundler-readme]: https://github.com/capistrano/bundler/blob/master/README.md