- r - 以节省内存的方式增长 data.frame
- ruby-on-rails - ruby/ruby on rails 内存泄漏检测
- android - 无法解析导入android.support.v7.app
- UNIX 域套接字与共享内存(映射文件)
我在 heroku 上上传了我的应用程序。但我面临一些问题。问题是什么:致命的:'priroda' 似乎不是 git 存储库?
~/priroda$ git pull
fatal: 'priroda' does not appear to be a git repository
fatal: The remote end hung up unexpectedly
~/priroda$ git remote -v
heroku git@heroku.com:secure-anchorage-3129.git (fetch)
heroku git@heroku.com:secure-anchorage-3129.git (push)
origin priroda (fetch)
origin priroda (push)
当我添加这个命令时:git push heroku master 我收到很多错误:
~/priroda$ git remote add origin git@heroku.com:secure-anchorage-3129.git
~/priroda$ git pull origin master
Initializing repository, done.
fatal: Couldn't find remote ref master
~/priroda$ git push heroku master
Initializing repository, done.
Counting objects: 117, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (104/104), done.
Writing objects: 100% (117/117), 126.46 KiB, done.
Total 117 (delta 16), reused 0 (delta 0)
-----> Ruby app detected
-----> Compiling Ruby/Rails
-----> Using Ruby version: ruby-2.0.0
-----> Installing dependencies using 1.6.3
Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
Your Gemfile lists the gem pg (>= 0) more than once.
You should probably keep only one of them.
While it's not a problem now, it could cause errors if you change the version of just one of them later.
Fetching gem metadata from https://rubygems.org/.......
Fetching additional metadata from https://rubygems.org/..
Installing multi_json 1.10.1
Installing rake 10.3.2
Installing i18n 0.6.9
Installing builder 3.0.4
Installing journey 1.0.4
Installing erubis 2.7.0
Installing hike 1.2.3
Installing rack 1.4.5
Installing tilt 1.4.1
Installing mime-types 1.25.1
Installing polyglot 0.3.5
Installing arel 3.0.3
Installing acts_as_indexed 0.8.3
Installing tzinfo 0.3.39
Installing addressable 2.3.6
Installing babosa 0.3.11
Installing coffee-script-source 1.7.0
Installing execjs 2.2.0
Installing thor 0.19.1
Installing orm_adapter 0.5.0
Installing excon 0.37.0
Installing bcrypt 3.1.7
Installing netrc 0.7.7
Installing json 1.8.1
Using bundler 1.6.3
Installing rubyzip 1.1.4
Installing rails_serve_static_assets 0.0.2
Installing rails_stdout_logging 0.0.3
Installing sass 3.3.8
Installing truncate_html 0.9.2
Installing will_paginate 3.0.5
Installing activesupport 3.2.18
Installing rails-i18n 0.7.4
Installing rack-cache 1.2
Installing rack-test 0.6.2
Installing rack-ssl 1.3.4
Installing warden 1.2.3
Installing dragonfly 0.9.15
Installing sprockets 2.2.2
Installing rest-client 1.6.7
Installing treetop 1.4.15
Installing launchy 2.4.2
Installing coffee-script 2.2.0
Installing bcrypt-ruby 3.1.5
Installing heroku-api 0.3.18
Installing uglifier 2.5.1
Installing rdoc 3.12.2
Installing rails_12factor 0.0.2
Installing activemodel 3.2.18
Installing mail 2.5.4
Installing heroku 3.8.4
Installing sdoc 0.3.20
Installing actionpack 3.2.18
Installing activerecord 3.2.18
Installing activeresource 3.2.18
Installing actionmailer 3.2.18
Installing routing-filter 0.3.1
Installing railties 3.2.18
Installing awesome_nested_set 2.1.6
Installing friendly_id 4.0.10.1
Installing globalize 3.1.0
Installing coffee-rails 3.2.2
Installing refinerycms-i18n 2.1.0
Installing devise 2.2.8
Installing decorators 1.0.3
Installing rails 3.2.18
Installing jquery-rails 2.3.0
Installing sass-rails 3.2.6
Installing seo_meta 1.4.0
Installing pg 0.17.1
Installing refinerycms-core 2.1.2
Installing refinerycms-dashboard 2.1.2
Installing refinerycms-authentication 2.1.2
Installing refinerycms-images 2.1.2
Installing refinerycms-pages 2.1.2
Installing refinerycms-resources 2.1.2
Installing refinerycms-acts-as-indexed 1.0.0
Installing refinerycms 2.1.2
Your bundle is complete!
Gems in the groups development and test were not installed.
It was installed into ./vendor/bundle
Post-install message from bcrypt-ruby:
#######################################################
The bcrypt-ruby gem has changed its name to just bcrypt. Instead of
installing `bcrypt-ruby`, you should install `bcrypt`. Please update your
dependencies accordingly.
#######################################################
Post-install message from rdoc:
Depending on your version of ruby, you may need to install ruby rdoc/ri data:
<= 1.8.6 : unsupported
= 1.8.7 : gem install rdoc-data; rdoc-data --install
= 1.9.1 : gem install rdoc-data; rdoc-data --install
>= 1.9.2 : nothing to do! Yay!
Post-install message from heroku:
! The `heroku` gem has been deprecated and replaced with the Heroku Toolbelt.
! Download and install from: https://toolbelt.heroku.com
! For API access, see: https://github.com/heroku/heroku.rb
Post-install message from friendly_id:
NOTE: FriendlyId 4.x breaks compatibility with 3.x. If you're upgrading
from 3.x, please see this document:
http://rubydoc.info/github/norman/friendly_id/master/file/WhatsNew.md
Post-install message from globalize:
Globalize has extracted versioning support to a separate gem named
globalize-versioning. If you are using versioning (with paper_trail
or any other versioning gem), please add the line
"gem 'globalize-versioning'" to your Gemfile and go to the github
page at globalize/globalize-versioning if you encounter any problems.
Note that the globalize-versioning gem does not delegate versions to
the translation table, so you will have to update your syntax to
the form: `post.translation.versions`. See the globalize-versioning
readme for details.
Bundle completed (25.95s)
Cleaning up the bundler cache.
-----> Writing config/database.yml to read from DATABASE_URL
-----> Preparing app for Rails asset pipeline
Running: rake assets:precompile
Connecting to database specified by DATABASE_URL
rake aborted!
PG::ConnectionBad: could not connect to server: Connection refused
Is the server running on host "127.0.0.1" and accepting
TCP/IP connections on port 5432?
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/postgresql_adapter.rb:1222:in `initialize'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/postgresql_adapter.rb:1222:in `new'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/postgresql_adapter.rb:1222:in `connect'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/postgresql_adapter.rb:324:in `initialize'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/postgresql_adapter.rb:28:in `new'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/postgresql_adapter.rb:28:in `postgresql_connection'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/abstract/connection_pool.rb:315:in `new_connection'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/abstract/connection_pool.rb:325:in `checkout_new_connection'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/abstract/connection_pool.rb:247:in `block (2 levels) in checkout'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/abstract/connection_pool.rb:242:in `loop'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/abstract/connection_pool.rb:242:in `block in checkout'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/abstract/connection_pool.rb:239:in `checkout'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/abstract/connection_pool.rb:102:in `block in connection'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/abstract/connection_pool.rb:101:in `connection'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/abstract/connection_pool.rb:410:in `retrieve_connection'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/abstract/connection_specification.rb:171:in `retrieve_connection'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/connection_adapters/abstract/connection_specification.rb:145:in `connection'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/model_schema.rb:310:in `clear_cache!'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.18/lib/active_record/railtie.rb:103:in `block (2 levels) in <class:Railtie>'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activesupport-3.2.18/lib/active_support/callbacks.rb:418:in `_run__2404055040551563881__prepare__433825113203608011__callbacks'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activesupport-3.2.18/lib/active_support/callbacks.rb:405:in `__run_callback'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activesupport-3.2.18/lib/active_support/callbacks.rb:385:in `_run_prepare_callbacks'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activesupport-3.2.18/lib/active_support/callbacks.rb:81:in `run_callbacks'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/actionpack-3.2.18/lib/action_dispatch/middleware/reloader.rb:74:in `prepare!'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/actionpack-3.2.18/lib/action_dispatch/middleware/reloader.rb:48:in `prepare!'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/railties-3.2.18/lib/rails/application/finisher.rb:47:in `block in <module:Finisher>'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/railties-3.2.18/lib/rails/initializable.rb:30:in `instance_exec'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/railties-3.2.18/lib/rails/initializable.rb:30:in `run'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/railties-3.2.18/lib/rails/initializable.rb:55:in `block in run_initializers'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/railties-3.2.18/lib/rails/initializable.rb:54:in `each'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/railties-3.2.18/lib/rails/initializable.rb:54:in `run_initializers'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/railties-3.2.18/lib/rails/application.rb:136:in `initialize!'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/railties-3.2.18/lib/rails/railtie/configurable.rb:30:in `method_missing'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/config/environment.rb:5:in `<top (required)>'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activesupport-3.2.18/lib/active_support/dependencies.rb:251:in `require'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activesupport-3.2.18/lib/active_support/dependencies.rb:251:in `block in require'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activesupport-3.2.18/lib/active_support/dependencies.rb:236:in `load_dependency'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/activesupport-3.2.18/lib/active_support/dependencies.rb:251:in `require'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/railties-3.2.18/lib/rails/application.rb:103:in `require_environment!'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/railties-3.2.18/lib/rails/application.rb:305:in `block (2 levels) in initialize_tasks'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/actionpack-3.2.18/lib/sprockets/assets.rake:93:in `block (2 levels) in <top (required)>'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/actionpack-3.2.18/lib/sprockets/assets.rake:60:in `block (3 levels) in <top (required)>'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/actionpack-3.2.18/lib/sprockets/assets.rake:23:in `invoke_or_reboot_rake_task'
/tmp/build_c4c36556-f948-4d00-9345-e2e4903f11f4/vendor/bundle/ruby/2.0.0/gems/actionpack-3.2.18/lib/sprockets/assets.rake:29:in `block (2 levels) in <top (required)>'
Tasks: TOP => environment
(See full trace by running task with --trace)
!
! Precompiling assets failed.
! Attempted to access a nonexistent database:
! https://devcenter.heroku.com/articles/pre-provision-database
!
! Push rejected, failed to compile Ruby app
To git@heroku.com:secure-anchorage-3129.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git@heroku.com:secure-anchorage-3129.git'
~/priroda$
最佳答案
您需要添加源远程:
删除当前的
git remote rm origin
添加 git 远程链接例如:(https://user@bitbucket.org/test.git 或 https://github.com/user/test.git)
git远程添加源链接
git pull origin master
(或其他分支)
如果你想从 heroku pull 你的应用程序
git pull heroku master
或者如果您尝试将新版本上传到 heroku
git push heroku master
[编辑]
请休假tutorial ,当您到达页面底部时,单击 Rails。
关于ruby-on-rails - Git pull 错误 : "fatal: Couldn' t find remote ref master"from Heroku,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/24451868/
我在 2 个不同的节点中设置了 master-master mysql 复制。假设如果我要再添加一个节点,即 3rd master ,我是否需要在新服务器中拥有与节点 1 和节点 2 中完全相同的数据
我认为我在理解 git 的基本概念方面是正确的。 我已经设置并克隆了一个远程存储库。我还创建了一个服务器端空存储库,并将我的本地存储库链接到它。 我的问题是我不明白: origin/master 与
从概念上讲,Master-Master 复制是如何工作的? 我认为碰撞将是一种需要以某种方式解决的常见事件。 最佳答案 主-主复制(更一般地——多主复制)在概念上的工作原理是假设冲突并不常见,并且只保
众所周知,mysql 是异步复制的。我听说我需要一些额外的插件来做 同步复制。 那么让我们考虑一下异步复制的情况:master 将事件写入其二进制日志,但不知道 master2 是否或何时检索并处理了
我正在寻求有关 MySql Master-Master 配置问题的帮助。 我正在处理由另一名员工设置的服务器配置,该员工现在无法就此事提供任何帮助。这是我第一次体验这样的设置,在做了相当多的研究之后,
尝试使用 HADOOP 运行 HBASE 时出现以下错误HBASE 0.98.xHADOOP 2.4.0 ERROR [main] master.HMasterCommandLine: Mas
停止独立 Spark Master 失败并显示以下消息: $ ./sbin/stop-master.sh no org.apache.spark.deploy.master.Master to sto
我不确定这是否是一个正常的分支场景,但是...... 假设我从 master 创建一个分支,比如分支 C,然后 merge 回其他先前存在的分支,比如分支 A 和 B,回到 master,然后我需要分
我无法推送到我的 git 存储库。 git clone和 git pull工作正常,但 git push不起作用。 我检查了其他答案,如 here尝试了几种方法,例如 git push origin
所以如果我在 master 中做: git checkout -b my-branch 并在那里做几次提交+推送。然后我做: git checkout master git pull 我现在能以某种方
我设置了 2 个 MYSQL 服务器: my.cnf server1: auto_increment_increment = 2 auto_increment_offset = 1 my.cnf se
我想知道一个服务器是否可以同时是slave和master。我们的问题是我们有很多移动单元需要同步到主服务器,但它们只需要主服务器上 100 个表中的 6 个。除了延迟同步和增加数据成本之外,所有额外的
我有主-主 Mysql 复制。每个主控复制其他主控。谁能解释一下为什么该主机上的 log-bin 文件不同? (尺寸差异很小)。谢谢! 最佳答案 嗯。我们决定使用 mysql 5.6 及其功能 - G
我正在努力理解这里的逻辑,如果术语不正确,我深表歉意。 我正在尝试构建一个功能类似于邮件的应用程序,IE: 所有邮箱 > 特定邮箱 > 消息 其中“所有邮箱”和“特定邮箱”占据 Controller
我一直在使用 master 分支进行开发,并希望将其清除为只有发布提交,以及它的用途。如何将所有内容从 master 复制到开发分支,然后重新启动 master? 最佳答案 Create develo
两周前,我创建了一个新分支,我们称它为exp。在此期间,exp 和 master 中都有几次提交。在此期间,exp 尚未更新 master 的更改 现在我想把所有从 exp 到 master 的更改都
我克隆:https://github.com/vy2014/git_lesson.git 然后我做了一些改动,尝试通过命令git push推送到远程服务器,但是错误: Counting objects
有没有好的方法来解释如何在 Git 中解决“![rejected] master -> master (fetch first)'”? 当我使用此命令时 $ git push origin maste
我该怎么办: 1)恢复推送到主(远程)的更改 2)将这些更改移动到单独的分支 3) 稍后将这些更改移回 master 最佳答案 首先做 2),但前提是你真的需要分支。 git branch chang
符号上有什么区别? 在我的一个工作站上,我克隆的 git 存储库显示(master),而另一个工作站则显示(master -> origin) 我还创建了一个新的本地存储库,提交了一个文本文件,提示仍
我是一名优秀的程序员,十分优秀!