You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently checking if the local dev environment setup with the given instructions works fine.
Running into the following errors when starting the new test machine (Win/Ub VM inst.):
14:16:42 unicorn.1 | config.eager_load is set to nil. Please update your config/environments/*.rb files accordingly:
14:16:42 unicorn.1 |
14:16:42 unicorn.1 | * development - set it to false
14:16:42 unicorn.1 | * test - set it to false (unless you use a tool that preloads your test environment)
14:16:42 unicorn.1 | * production - set it to true
[...]
14:16:42 unicorn.1 | :6379/0/cache (URI::InvalidURIError)vm/rubies/ruby-2.1.2/lib/ruby/2.1.0/uri/common.rb:176:in `split': bad URI(is not URI?): redis://localhost
config.eager_load is set in all environment files.
The test machine is running ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux]
A redis instance is also running (redis-server start/running, process 1031)
Will have to look into this later this week.
The text was updated successfully, but these errors were encountered:
I'm forgetting about the damn line endings every time...
For reference:
Text files created on DOS/Windows machines have different line endings than files created on Unix/Linux. DOS uses carriage return and line feed ("\r\n") as a line ending, which Unix uses just line feed ("\n"). You need to be careful about transferring files between Windows machines and Unix machines to make sure the line endings are translated properly.
I'm currently checking if the local dev environment setup with the given instructions works fine.
Running into the following errors when starting the new test machine (Win/Ub VM inst.):
config.eager_load
is set in all environment files.The test machine is running
ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-linux]
A redis instance is also running (
redis-server start/running, process 1031
)Will have to look into this later this week.
The text was updated successfully, but these errors were encountered: