Permalink
Browse files

Merge pull request #1992 from will-in-wi/https_docs

Switch a number of http links and dependencies to https
  • Loading branch information...
will-in-wi committed Jun 24, 2018
2 parents 5bab343 + 04455d9 commit 220db8fabab15b9d5cd5c9ab1f2744e0aa346eb0
View
@@ -1,6 +1,6 @@
# capistranorb.com
-This `docs/` directory generates the [capistranorb.com](http://capistranorb.com/) site. Feel free to send pull requests to make improvements to Capistrano's documentation!
+This `docs/` directory generates the [capistranorb.com](https://capistranorb.com/) site. Feel free to send pull requests to make improvements to Capistrano's documentation!
### Quick start
@@ -10,7 +10,7 @@
<div class="large-4 columns">
<ul>
- <li><a href="http://stackoverflow.com/questions/tagged/capistrano">StackOverflow</a></li>
+ <li><a href="https://stackoverflow.com/questions/tagged/capistrano">StackOverflow</a></li>
<li><a href="https://groups.google.com/forum/#!forum/capistrano">Mailing List</a></li>
</ul>
</div>
@@ -5,7 +5,7 @@
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>{{ page.title }}</title>
- <link href='http://fonts.googleapis.com/css?family=Enriqueta' rel='stylesheet' type='text/css'>
+ <link href='https://fonts.googleapis.com/css?family=Enriqueta' rel='stylesheet' type='text/css'>
<script type="text/javascript" src="//use.typekit.net/itm5ubu.js"></script>
<script type="text/javascript">try{Typekit.load();}catch(e){}</script>
<link rel="stylesheet" href="/css/foundation.css" />
@@ -37,7 +37,7 @@ Read more about this:
* [At Sam Stephenson's excellent *Unix shell initialization* wiki
page](https://github.com/sstephenson/rbenv/wiki/Unix-shell-initialization)
* [Interactive and non-interactive shells and scripts
- documentation](http://www.tldp.org/LDP/abs/html/intandnonint.html)
+ documentation](https://www.tldp.org/LDP/abs/html/intandnonint.html)
## How does what Capistrano does differ from an SSH session
@@ -54,7 +54,7 @@ login` shell, the exact opposite of what we need for Capistrano!
## How can I check?
I actually had to look this up, most of the time it's common sense, but
-[stackoverflow to the rescue](http://unix.stackexchange.com/a/26782), let's
+[stackoverflow to the rescue](https://unix.stackexchange.com/a/26782), let's
figure this out!
First, we'll try a *real* SSH session, logging in via our terminal, and seeing
@@ -50,7 +50,7 @@ correct, we are allowed to login.
2. Open "Git Bash" and follow next instructions always inside Git Bash prompt.
3. Activate ssh-agent: ```$ eval "$(ssh-agent -s)" ```
-**Note:** If you want to use [Putty tool](http://www.putty.org/) to connect to remote server (from Windows) with ssh keys, then you need to generate ppk file, through puttygen tool.
+**Note:** If you want to use [Putty tool](https://www.putty.org/) to connect to remote server (from Windows) with ssh keys, then you need to generate ppk file, through puttygen tool.
**Hint:** If you have more than one developer in your team, they should all add their
@@ -119,7 +119,7 @@ none, other none), in the `~/.ssh` directory which needs the permissions
`0700` (owner read/write/execute, group none, other none).
If you are on linux there often exists a command
-[`ssh-copy-id`](http://linux.die.net/man/1/ssh-copy-id) which streamlines this
+[`ssh-copy-id`](https://linux.die.net/man/1/ssh-copy-id) which streamlines this
process, otherwise the workflow is something like:
```bash
@@ -68,7 +68,7 @@ You can test this using a ssh client, e.g. `ssh myuser@destinationserver`. If
you cannot connect at all, you may need to set up the SSH server or resolve
firewall/network issues. Look for a tutorial (here are suggestions for
[Ubuntu](https://help.ubuntu.com/community/SSH) and
-[RedHat/CentOS](http://www.cyberciti.biz/faq/centos-ssh/)).
+[RedHat/CentOS](https://www.cyberciti.biz/faq/centos-ssh/)).
If a password is requested when you log in, you may need to set up SSH keys.
GitHub has a [good tutorial](https://help.github.com/articles/generating-ssh-keys/)
@@ -77,7 +77,7 @@ key to `~/.ssh/authorized_keys` on the destination server as the deployment user
(append on a new line).
More information on SSH and login is available via the
-[Authentication and Authorisation](http://capistranorb.com/documentation/getting-started/authentication-and-authorisation/)
+[Authentication and Authorisation](https://capistranorb.com/documentation/getting-started/authentication-and-authorisation/)
section of the guide.
If you are still struggling to get login working, try the
@@ -170,7 +170,7 @@ are deploying to can reach.
Here's how this might look in a typical example: note that we'll cover
authentication in the next chapter, but for now we'll assume this repository is
open source, taking an example application from the [Rails Examples and
-Tutorials](http://railsapps.github.io/) site. There we'll find maintained a
+Tutorials](https://railsapps.github.io/) site. There we'll find maintained a
handful of typical Rails apps with typical dependencies.
The Rails application they host, which uses Devise (for authentication) and
@@ -11,7 +11,7 @@ When a deployment is run, Capistrano executes one task at a time on all servers
If the error occurs during a deployment task which is prior to the final cutover, for example during creation of symlinks, the process will simply stop and the previously deployed application will continue to run. However if the failing deployment task is after `deploy:symlink:release`, during which the `current` symlink is moved to the newly deployed code, this may result in an inconsistent state which may be solved by executing `cap [stage] deploy:rollback`. Rollback can also be a solution for issues with failed deployments due to buggy code or other reasons.
-Per http://capistranorb.com/documentation/getting-started/flow/, the standard deployment and rollback processes are nearly identical. The difference is that in a deploy, the `deploy:updating` and `deploy:updated` tasks are executed, while in a rollback, the `deploy:reverting` and `deploy:reverted` (a hook task) tasks are run. Also, instead of `deploy:finishing`, `deploy:finishing_rollback` is run, as cleanup can sometimes be different.
+Per https://capistranorb.com/documentation/getting-started/flow/, the standard deployment and rollback processes are nearly identical. The difference is that in a deploy, the `deploy:updating` and `deploy:updated` tasks are executed, while in a rollback, the `deploy:reverting` and `deploy:reverted` (a hook task) tasks are run. Also, instead of `deploy:finishing`, `deploy:finishing_rollback` is run, as cleanup can sometimes be different.
### `deploy:reverting`

0 comments on commit 220db8f

Please sign in to comment.