diff --git a/docs/README.md b/docs/README.md index f8ecd469..1147a57a 100644 --- a/docs/README.md +++ b/docs/README.md @@ -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 diff --git a/docs/_includes/footer.html b/docs/_includes/footer.html index d6218eb4..c53f8572 100644 --- a/docs/_includes/footer.html +++ b/docs/_includes/footer.html @@ -10,7 +10,7 @@
diff --git a/docs/_layouts/default.html b/docs/_layouts/default.html index 7f8a5d8a..383b9548 100644 --- a/docs/_layouts/default.html +++ b/docs/_layouts/default.html @@ -5,7 +5,7 @@ {{ page.title }} - + diff --git a/docs/documentation/faq/why-does-something-work-in-my-ssh-session-but-not-in-capistrano/index.markdown b/docs/documentation/faq/why-does-something-work-in-my-ssh-session-but-not-in-capistrano/index.markdown index ae4631ee..2cef0a3e 100644 --- a/docs/documentation/faq/why-does-something-work-in-my-ssh-session-but-not-in-capistrano/index.markdown +++ b/docs/documentation/faq/why-does-something-work-in-my-ssh-session-but-not-in-capistrano/index.markdown @@ -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 diff --git a/docs/documentation/getting-started/authentication-and-authorisation/index.markdown b/docs/documentation/getting-started/authentication-and-authorisation/index.markdown index 505c9031..d9ac32cb 100644 --- a/docs/documentation/getting-started/authentication-and-authorisation/index.markdown +++ b/docs/documentation/getting-started/authentication-and-authorisation/index.markdown @@ -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 diff --git a/docs/documentation/getting-started/installation/index.markdown b/docs/documentation/getting-started/installation/index.markdown index 165e5a28..c02ea439 100644 --- a/docs/documentation/getting-started/installation/index.markdown +++ b/docs/documentation/getting-started/installation/index.markdown @@ -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 diff --git a/docs/documentation/getting-started/preparing-your-application/index.markdown b/docs/documentation/getting-started/preparing-your-application/index.markdown index 1f60e05e..1babc803 100644 --- a/docs/documentation/getting-started/preparing-your-application/index.markdown +++ b/docs/documentation/getting-started/preparing-your-application/index.markdown @@ -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 diff --git a/docs/documentation/getting-started/rollbacks/index.markdown b/docs/documentation/getting-started/rollbacks/index.markdown index 780111ef..b47a872b 100644 --- a/docs/documentation/getting-started/rollbacks/index.markdown +++ b/docs/documentation/getting-started/rollbacks/index.markdown @@ -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`