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

fix external links

Browse source
This commit is contained in:
Thomas Kriechbaumer 2015-01-22 15:23:09 +00:00
parent 4eb7e72c4a
commit 9c4ede2561
3 changed files with 10 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
_posts/2013-06-01-release-announcement.markdown
View file

@ -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:

20
documentation/getting-started/cold-start/index.markdown
View file

@ -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

2
documentation/getting-started/installation/index.markdown
View file

@ -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