mastodon/config/boot.rb

# frozen_string_literal: true

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/setup' # Speed up boot time by caching expensive operations.
Enable Rubocop Style/FrozenStringLiteralComment (#23793) 2023-07-12 03:47:08 -04:00			`# frozen_string_literal: true`

Add clean error message when RAILS_ENV is unset (#15381) 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> 2020-12-20 18:05:03 +01:00			`unless ENV.key?('RAILS_ENV')`
			`STDERR.puts 'ERROR: Missing RAILS_ENV environment variable, please set it to "production", "development", or "test".'`
			`exit 1`
			`end`

Upgrade to Rails 5.0.0.1 2016-08-17 17:56:23 +02:00			`ENV['BUNDLE_GEMFILE'] \|\|= File.expand_path('../Gemfile', __dir__)`
Initial commit 2016-02-20 22:53:20 +01:00
Lint pass (#8876) 2018-10-04 20:36:53 +10:00			`require 'bundler/setup' # Set up gems listed in the Gemfile.`
Use default `bootsnap/setup` in boot.rb (#25502) 2023-06-22 12:46:32 -04:00			`require 'bootsnap/setup' # Speed up boot time by caching expensive operations.`