Merge branch 'bw-fix-script-path' into 'master'

fix references to script location

See merge request gitlab-com/migration!181

README.md

@@ -183,8 +183,8 @@ Before a failover, the coordinator needs to login to the deploy host:
 
 Then carry out the following steps:
 
-1.  **Setup `bin/source_vars`**: `test -f /opt/gitlab-migration/bin/source_vars || sudo cp /opt/gitlab-migration/bin/source_vars_template.sh /opt/gitlab-migration/bin/source_vars`
-1.  **Configure `vi /opt/gitlab-migration/bin/source_vars`**: The variables are explained in the file. Since this contains secrets, this file should not be checked in. (it's `.gitignore`'d)
-1.  **Verify `/opt/gitlab-migration/bin/verify-failover-config`**: You should receive a message indicating success
-1.  **Setup the workflow issues**": Run `/opt/gitlab-migration/bin/start-failover-procedure.sh`. This will setup several issues in the issue tracker for performing the checks, failover, tests, etc.
+1.  **Setup `bin/source_vars`**: `test -f /opt/gitlab-migration/migration/bin/source_vars || sudo cp /opt/gitlab-migration/migration/bin/source_vars_template.sh /opt/gitlab-migration/migration/bin/source_vars`
+1.  **Configure `sudo vi /opt/gitlab-migration/migration/bin/source_vars`**: The variables are explained in the file. Since this contains secrets, this file should not be checked in. (it's `.gitignore`'d)
+1.  **Verify `/opt/gitlab-migration/migration/bin/verify-failover-config`**: You should receive a message indicating success
+1.  **Setup the workflow issues**": Run `/opt/gitlab-migration/migration/bin/start-failover-procedure.sh`. This will setup several issues in the issue tracker for performing the checks, failover, tests, etc.
     * Any variables in the template in the format `__VARIABLE__` will be substituted with their values from the `bin/source_vars` file, saving manual effort.