讓Puma Postgres服務器在開發過程中與Heroku合作，還是回到Sqlite上有意義？

Question

我得到了使用puma而不是rails s一段時間工作良好，但後來開發和代碼更改和刷新在某些時候刷新不起作用，推遲很長時間。我以爲它已經崩潰或什麼了，所以我殺了彪馬服務器，但後來它說'優雅地關閉'幾分鐘，所以我殺死了終端窗口。然後，在我嘗試使用puma的新窗口中，它表示主機已被佔用，因此該過程仍在運行。無法找到它的位置，我重新啓動了電腦。重新啓動後，我現在得到錯誤An unhandled lowlevel error occured. The application logs may have details.或PG::ConnectionBad fe_sendauth: no password supplied，這取決於我運行的是puma還是RAILS_ENV=development puma。

這些回答都沒有意義，我看到其他人在rake db:migrate上發生的這個錯誤。所以，我想遷移數據庫，並得到了同樣的錯誤PG::ConnectionBad: fe_sendauth: no password supplied

並在日誌中嘗試運行服務器時：Rack app error: #<RuntimeError: Missing secret_key_base for 'production' environment, set this value in配置/ secrets.yml >

現在，這使最有意義的我，作爲爲什麼puma默認運行生產環境，並且需要一個特殊的命令才能在開發中運行？

production: 
    secret_key_base: <%= ENV["SECRET_KEY_BASE"] %> 

依賴於Heroku傳遞secret_key_base是我的假設，所以它不適用於開發。但後來甚至RAILS_ENV=development puma拋出

PG::ConnectionBad 
fe_sendauth: no password supplied 

而且不會出現一絲幫我：

activerecord (4.1.7) lib/active_record/connection_adapters/postgresql_adapter.rb:888:in `initialize' 
activerecord (4.1.7) lib/active_record/connection_adapters/postgresql_adapter.rb:888:in `new' 
activerecord (4.1.7) lib/active_record/connection_adapters/postgresql_adapter.rb:888:in `connect' 
activerecord (4.1.7) lib/active_record/connection_adapters/postgresql_adapter.rb:568:in `initialize' 
activerecord (4.1.7) lib/active_record/connection_adapters/postgresql_adapter.rb:41:in `new' 
activerecord (4.1.7) lib/active_record/connection_adapters/postgresql_adapter.rb:41:in `postgresql_connection' 
activerecord (4.1.7) lib/active_record/connection_adapters/abstract/connection_pool.rb:435:in `new_connection' 
activerecord (4.1.7) lib/active_record/connection_adapters/abstract/connection_pool.rb:445:in `checkout_new_connection' 
activerecord (4.1.7) lib/active_record/connection_adapters/abstract/connection_pool.rb:416:in `acquire_connection' 
activerecord (4.1.7) lib/active_record/connection_adapters/abstract/connection_pool.rb:351:in `block in checkout' 
/Users/lasernite/.rvm/rubies/ruby-2.1.4/lib/ruby/2.1.0/monitor.rb:211:in `mon_synchronize' 
activerecord (4.1.7) lib/active_record/connection_adapters/abstract/connection_pool.rb:350:in `checkout' 
activerecord (4.1.7) lib/active_record/connection_adapters/abstract/connection_pool.rb:265:in `block in connection' 
/Users/lasernite/.rvm/rubies/ruby-2.1.4/lib/ruby/2.1.0/monitor.rb:211:in `mon_synchronize' 
activerecord (4.1.7) lib/active_record/connection_adapters/abstract/connection_pool.rb:264:in `connection' 
activerecord (4.1.7) lib/active_record/connection_adapters/abstract/connection_pool.rb:541:in `retrieve_connection' 
activerecord (4.1.7) lib/active_record/connection_handling.rb:113:in `retrieve_connection' 
activerecord (4.1.7) lib/active_record/connection_handling.rb:87:in `connection' 
activerecord (4.1.7) lib/active_record/migration.rb:388:in `check_pending!' 
activerecord (4.1.7) lib/active_record/migration.rb:377:in `call' 
actionpack (4.1.7) lib/action_dispatch/middleware/callbacks.rb:29:in `block in call' 
activesupport (4.1.7) lib/active_support/callbacks.rb:82:in `run_callbacks' 
actionpack (4.1.7) lib/action_dispatch/middleware/callbacks.rb:27:in `call' 
actionpack (4.1.7) lib/action_dispatch/middleware/reloader.rb:73:in `call' 
actionpack (4.1.7) lib/action_dispatch/middleware/remote_ip.rb:76:in `call' 
actionpack (4.1.7) lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call' 
actionpack (4.1.7) lib/action_dispatch/middleware/show_exceptions.rb:30:in `call' 
railties (4.1.7) lib/rails/rack/logger.rb:38:in `call_app' 
railties (4.1.7) lib/rails/rack/logger.rb:20:in `block in call' 
activesupport (4.1.7) lib/active_support/tagged_logging.rb:68:in `block in tagged' 
activesupport (4.1.7) lib/active_support/tagged_logging.rb:26:in `tagged' 
activesupport (4.1.7) lib/active_support/tagged_logging.rb:68:in `tagged' 
railties (4.1.7) lib/rails/rack/logger.rb:20:in `call' 
actionpack (4.1.7) lib/action_dispatch/middleware/request_id.rb:21:in `call' 
rack (1.5.2) lib/rack/methodoverride.rb:21:in `call' 
rack (1.5.2) lib/rack/runtime.rb:17:in `call' 
activesupport (4.1.7) lib/active_support/cache/strategy/local_cache_middleware.rb:26:in `call' 
rack (1.5.2) lib/rack/lock.rb:17:in `call' 
actionpack (4.1.7) lib/action_dispatch/middleware/static.rb:84:in `call' 
rack (1.5.2) lib/rack/sendfile.rb:112:in `call' 
rack-timeout (0.2.0) lib/rack/timeout.rb:108:in `call' 
railties (4.1.7) lib/rails/engine.rb:514:in `call' 
railties (4.1.7) lib/rails/application.rb:144:in `call' 
puma (2.11.0) lib/puma/configuration.rb:82:in `call' 
puma (2.11.0) lib/puma/server.rb:507:in `handle_request' 
puma (2.11.0) lib/puma/server.rb:375:in `process_client' 
puma (2.11.0) lib/puma/server.rb:262:in `block in run' 
puma (2.11.0) lib/puma/thread_pool.rb:104:in `call' 
puma (2.11.0) lib/puma/thread_pool.rb:104:in `block in spawn_thread' 

我卡在那裏，試圖解決此錯誤。

請給出任何見解，你可以。謝謝！

Answer 1

您的「config/secrets.yml」文件列於.gitignore？ Heroku需要該文件。從.gitignore刪除或註釋它。我有同樣的問題，這是我的問題。

而且，看到這個帖子了相同的答案： How to solve error "Missing `secret_key_base` for 'production' environment" (Rails 4.1)

祝你好運！