Question

最近，我正在研究的一个项目改变了Github上的源代码库。

deploy.rb已更新为正确指向新的github帐户，但当我运行cap staging deploy时，它会查找旧的repo。

cap staging deploy
      * executing `staging'
      * executing `deploy'
      * executing `deploy:updatify'
      * executing "cd /home/deploy/example/current; git fetch origin; git reset --hard origin/staging"
        servers: ["example.com"]
        Password: 
        [example.com] executing command
     ** [out :: example.com] ERROR: oldusername/example.git doesn't exist. Did you enter it correctly?
     ** [out :: example.com] fatal: The remote end hung up unexpectedly
     ** [out :: example.com] HEAD is now at 7c92a69 adding changes
        command finished in 4148ms
        triggering after callbacks for `deploy:updatify'
      * executing `bundle:install'
      * executing "cd /home/deploy/example/current && bundle install --gemfile /home/deploy/example/current/Gemfile --path /home/deploy/example/shared/bundle --deployment --quiet --without development test"
        servers: ["example.com"]
        [example.com] executing command
        command finished in 7442ms
      * executing `deploy:restart'
      * executing "cd /home/deploy/example/current; [ -f tmp/pids/unicorn.pid ] && kill -USR2 `cat tmp/pids/unicorn.pid` || bundle exec unicorn_rails -c ./config/unicorn.rb -E staging -D"
        servers: ["example.com"]
        [example.com] executing command
        command finished in 94ms

我试图查找这里提到的缓存副本目录：Capistrano still trying to connect to my old repo但是在我的服务器上，没有缓存副本目录。

它仍然在哪里引用旧存储库？

deploy.rb：

 require 'bundler/capistrano'

 load 'config/deploy/nginx'
 load 'config/deploy/unicorn'
 load 'config/deploy/updatify'

 # Base Settings ############################################################

 set :user,          'deploy'
 set :application,   'example'
 set :use_sudo,      false
 set :scm,           :git
 set :repository,    'git@github.com:new_repo_user/example.git'
 set :deploy_to,     "/home/#{user}/#{application}"

 # Fake using releases to just use git
 set :current_release, current_path

 ssh_options[:paranoid] = false
 default_run_options[:pty] = true

 # Multistage ###############################################################    ###

 task :production do
   server 'exampleprod.com', :app, :web, :db, :primary => true
   set  :branch,      'origin/production'
   set  :environment, 'production'
   set  :environment_database, defer { production_database }
   set  :environment_dbhost,   defer { production_dbhost }
 end

 task :staging do
   server 'example.com', :app, :web, :db, :primary => true
   set :branch,      'origin/staging'
   set :environment, 'staging'
   set :environment_database, defer { environment_info["database"] }
   set :environment_dbhost,   defer { environment_info["host"] }
 end

Answer 1

事实证明，.git/config文件中仍然存在对原始存储库的引用。

我改变了这个：

[remote "origin"]
        fetch = +refs/heads/*:refs/remotes/origin/*
        url = git@github.com:oldusername/example.git

对此：

[remote "origin"]
        fetch = +refs/heads/*:refs/remotes/origin/*
        url = git@github.com:new_repo_user/example.git

Capistrano开始做正确的事。

Answer 2

更改存储库组后，我遇到了类似的问题。事实证明，从服务器删除repo目录修复了旧的repo版本引用的问题。

部署后，Capistrano寻找旧的Github仓库.rb改为新的仓库

2 个答案: