9734c9b6fe
By default, an unset RAILS_ENV is understood as RAILS_ENV=development. However, this is not what most people expect, and due to development-only dependencies, users are often left with confusing error messages. This commit changes it so that an explicit RAILS_ENV is required, and failing that, an error message is displayed before loading the app. Co-authored-by: Claire <claire.github-309c@sitedethib.com>
20 lines
682 B
Ruby
20 lines
682 B
Ruby
unless ENV.key?('RAILS_ENV')
|
|
STDERR.puts 'ERROR: Missing RAILS_ENV environment variable, please set it to "production", "development", or "test".'
|
|
exit 1
|
|
end
|
|
|
|
ENV['BUNDLE_GEMFILE'] ||= File.expand_path('../Gemfile', __dir__)
|
|
|
|
require 'bundler/setup' # Set up gems listed in the Gemfile.
|
|
require 'bootsnap' # Speed up boot time by caching expensive operations.
|
|
|
|
Bootsnap.setup(
|
|
cache_dir: File.expand_path('../tmp/cache', __dir__),
|
|
development_mode: ENV.fetch('RAILS_ENV', 'development') == 'development',
|
|
load_path_cache: true,
|
|
autoload_paths_cache: true,
|
|
disable_trace: false,
|
|
compile_cache_iseq: false,
|
|
compile_cache_yaml: false
|
|
)
|