railties 7.1.3.4 → 7.2.0.beta1

data/lib/rails/app_updater.rb

@@ -1,40 +0,0 @@
-# frozen_string_literal: true
-
-require "rails/generators"
-require "rails/generators/rails/app/app_generator"
-
-module Rails
-  class AppUpdater # :nodoc:
-    class << self
-      def invoke_from_app_generator(method)
-        app_generator.send(method)
-      end
-
-      def app_generator
-        @app_generator ||= begin
-          gen = Rails::Generators::AppGenerator.new ["rails"], generator_options, destination_root: Rails.root
-          gen.send(:valid_const?) unless File.exist?(Rails.root.join("config", "application.rb"))
-          gen
-        end
-      end
-
-      private
-        def generator_options
-          options = { api: !!Rails.application.config.api_only, update: true }
-          options[:name]                = Rails.application.class.name.chomp("::Application").underscore
-          options[:skip_active_job]     = !defined?(ActiveJob::Railtie)
-          options[:skip_active_record]  = !defined?(ActiveRecord::Railtie)
-          options[:skip_active_storage] = !defined?(ActiveStorage::Engine)
-          options[:skip_action_mailer]  = !defined?(ActionMailer::Railtie)
-          options[:skip_action_mailbox] = !defined?(ActionMailbox::Engine)
-          options[:skip_action_text]    = !defined?(ActionText::Engine)
-          options[:skip_action_cable]   = !defined?(ActionCable::Engine)
-          options[:skip_test]           = !defined?(Rails::TestUnitRailtie)
-          options[:skip_system_test]    = Rails.application.config.generators.system_tests.nil?
-          options[:skip_asset_pipeline] = !defined?(Sprockets::Railtie) && !defined?(Propshaft::Railtie)
-          options[:skip_bootsnap]       = !defined?(Bootsnap)
-          options
-        end
-    end
-  end
-end

data/lib/rails/commands/secrets/USAGE

@@ -1,61 +0,0 @@
-Description:
-    ** DEPRECATED **
-    Rails 5.2 has introduced a new `credentials` API that replaces Rails secrets.
-    Please use the Rails `credentials` commands instead.
-    Run `bin/rails credentials:help` for more information.
-
-    The Rails `secrets` commands helps encrypting secrets to slim a production
-    environment's `ENV` hash. It's also useful for atomic deploys: no need to
-    coordinate key changes to get everything working as the keys are shipped
-    with the code.
-
-Setup:
-    Run `<%= executable(:setup) %>` to opt in and generate the `config/secrets.yml.key`
-    and `config/secrets.yml.enc` files.
-
-    The latter contains all the keys to be encrypted while the former holds the
-    encryption key.
-
-    Don't lose the key! Put it in a password manager your team can access.
-    Should you lose it no one, including you, will be able to access any encrypted
-    secrets.
-    Don't commit the key! Add `config/secrets.yml.key` to your source control's
-    ignore file. If you use Git, Rails handles this for you.
-
-    Rails also looks for the key in `ENV["RAILS_MASTER_KEY"]` if that's easier to
-    manage.
-
-    You could prepend that to your server's start command like this:
-
-        RAILS_MASTER_KEY="im-the-master-now-hahaha" bin/rails server
-
-    The `config/secrets.yml.enc` has much the same format as `config/secrets.yml`:
-
-        production:
-          secret_key_base: so-secret-very-hidden-wow
-          payment_processing_gateway_key: much-safe-very-gaedwey-wow
-
-    But that's where the similarities between `secrets.yml` and `secrets.yml.enc`
-    end, e.g. no keys from `secrets.yml` will be moved to `secrets.yml.enc` and
-    be encrypted.
-
-    A `shared:` top level key is also supported such that any keys there is merged
-    into the other environments.
-
-    Additionally, Rails won't read encrypted secrets out of the box even if you have
-    the key. Add this:
-
-        config.read_encrypted_secrets = true
-
-    to the environment you'd like to read encrypted secrets. `<%= executable(:setup) %>`
-    inserts this into the production environment by default.
-
-Editing Secrets:
-    After `<%= executable(:setup) %>`, run `<%= executable(:edit) %>`.
-
-    That command opens a temporary file in `$VISUAL` or `$EDITOR` with the decrypted
-    contents of `config/secrets.yml.enc` to edit the encrypted secrets.
-
-    When the temporary file is next saved the contents are encrypted and written to
-    `config/secrets.yml.enc` while the file itself is destroyed to prevent secrets
-    from leaking.

data/lib/rails/commands/secrets/secrets_command.rb

@@ -1,47 +0,0 @@
-# frozen_string_literal: true
-
-require "active_support"
-require "active_support/core_ext/string/filters"
-require "rails/secrets"
-require "rails/command/helpers/editor"
-
-module Rails
-  module Command
-    class SecretsCommand < Rails::Command::Base # :nodoc:
-      include Helpers::Editor
-
-      desc "edit", "**deprecated** Open the secrets in `$VISUAL` or `$EDITOR` for editing"
-      def edit
-        Rails.deprecator.warn(<<~MSG.squish)
-          `bin/rails secrets:edit` is deprecated in favor of credentials and will be removed in Rails 7.2.
-          Run `bin/rails credentials:help` for more information.
-        MSG
-
-        boot_application!
-
-        using_system_editor do
-          Rails::Secrets.read_for_editing { |tmp_path| system_editor(tmp_path) }
-          say "File encrypted and saved."
-        end
-      rescue Rails::Secrets::MissingKeyError => error
-        say error.message
-      rescue Errno::ENOENT => error
-        if error.message.include?("secrets.yml.enc")
-          exit 1
-        else
-          raise
-        end
-      end
-
-      desc "show", "**deprecated** Show the decrypted secrets"
-      def show
-        Rails.deprecator.warn(<<~MSG.squish)
-          `bin/rails secrets:show` is deprecated in favor of credentials and will be removed in Rails 7.2.
-          Run `bin/rails credentials:help` for more information.
-        MSG
-
-        say Rails::Secrets.read
-      end
-    end
-  end
-end

data/lib/rails/generators/rails/app/templates/config/databases/jdbc.yml.tt

@@ -1,68 +0,0 @@
-# If you are using mssql, derby, hsqldb, or h2 with one of the
-# ActiveRecord JDBC adapters, install the appropriate driver, e.g.,:
-#   gem install activerecord-jdbcmssql-adapter
-#
-# Configure using Gemfile:
-#   gem "activerecord-jdbcmssql-adapter"
-#
-# development:
-#   adapter: mssql
-#   username: <%= app_name %>
-#   password:
-#   host: localhost
-#   database: <%= app_name %>_development
-#
-# Warning: The database defined as "test" will be erased and
-# re-generated from your development database when you run "rake".
-# Do not set this db to the same as development or production.
-#
-# test:
-#   adapter: mssql
-#   username: <%= app_name %>
-#   password:
-#   host: localhost
-#   database: <%= app_name %>_test
-#
-# production:
-#   adapter: mssql
-#   username: <%= app_name %>
-#   password:
-#   host: localhost
-#   database: <%= app_name %>_production
-
-# If you are using oracle, db2, sybase, informix or prefer to use the plain
-# JDBC adapter, configure your database setting as the example below (requires
-# you to download and manually install the database vendor's JDBC driver .jar
-# file). See your driver documentation for the appropriate driver class and
-# connection string:
-
-default: &default
-  adapter: jdbc
-  pool: <%%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
-  username: <%= app_name %>
-  password:
-  driver:
-
-development:
-  <<: *default
-  url: jdbc:db://localhost/<%= app_name %>_development
-
-# Warning: The database defined as "test" will be erased and
-# re-generated from your development database when you run "rake".
-# Do not set this db to the same as development or production.
-test:
-  <<: *default
-  url: jdbc:db://localhost/<%= app_name %>_test
-
-# As with config/credentials.yml, you never want to store sensitive information,
-# like your database password, in your source code. If your source code is
-# ever seen by anyone, they now have access to your database.
-#
-# Instead, provide the password as an environment variable when you boot the
-# app. Read https://guides.rubyonrails.org/configuring.html#configuring-a-database
-# for a full overview on how database connection configuration can be specified.
-#
-production:
-  url: jdbc:db://localhost/<%= app_name %>_production
-  username: <%= app_name %>
-  password: <%%= ENV["<%= app_name.upcase %>_DATABASE_PASSWORD"] %>

data/lib/rails/generators/rails/app/templates/config/databases/jdbcmysql.yml.tt

@@ -1,54 +0,0 @@
-# MySQL. Versions 5.5.8 and up are supported.
-#
-# Install the MySQL driver:
-#   gem install activerecord-jdbcmysql-adapter
-#
-# Configure Using Gemfile
-# gem "activerecord-jdbcmysql-adapter"
-#
-# And be sure to use new-style password hashing:
-#   https://dev.mysql.com/doc/refman/5.7/en/password-hashing.html
-#
-default: &default
-  adapter: mysql
-  pool: <%%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
-  username: root
-  password:
-  host: localhost
-
-development:
-  <<: *default
-  database: <%= app_name %>_development
-
-# Warning: The database defined as "test" will be erased and
-# re-generated from your development database when you run "rake".
-# Do not set this db to the same as development or production.
-test:
-  <<: *default
-  database: <%= app_name %>_test
-
-# As with config/credentials.yml, you never want to store sensitive information,
-# like your database password, in your source code. If your source code is
-# ever seen by anyone, they now have access to your database.
-#
-# Instead, provide the password or a full connection URL as an environment
-# variable when you boot the app. For example:
-#
-#   DATABASE_URL="mysql://myuser:mypass@localhost/somedatabase"
-#
-# If the connection URL is provided in the special DATABASE_URL environment
-# variable, Rails will automatically merge its configuration values on top of
-# the values provided in this file. Alternatively, you can specify a connection
-# URL environment variable explicitly:
-#
-#   production:
-#     url: <%%= ENV["MY_APP_DATABASE_URL"] %>
-#
-# Read https://guides.rubyonrails.org/configuring.html#configuring-a-database
-# for a full overview on how database connection configuration can be specified.
-#
-production:
-  <<: *default
-  database: <%= app_name %>_production
-  username: <%= app_name %>
-  password: <%%= ENV["<%= app_name.upcase %>_DATABASE_PASSWORD"] %>

data/lib/rails/generators/rails/app/templates/config/databases/jdbcpostgresql.yml.tt

@@ -1,70 +0,0 @@
-# PostgreSQL. Versions 9.3 and up are supported.
-#
-# Configure Using Gemfile
-# gem "activerecord-jdbcpostgresql-adapter"
-#
-default: &default
-  adapter: postgresql
-  encoding: unicode
-  pool: <%%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
-
-development:
-  <<: *default
-  database: <%= app_name %>_development
-
-  # The specified database role being used to connect to PostgreSQL.
-  # To create additional roles in PostgreSQL see `$ createuser --help`.
-  # When left blank, PostgreSQL will use the default role. This is
-  # the same name as the operating system user running Rails.
-  #username: <%= app_name %>
-
-  # The password associated with the PostgreSQL role (username).
-  #password:
-
-  # Connect on a TCP socket. Omitted by default since the client uses a
-  # domain socket that doesn't need configuration. Windows does not have
-  # domain sockets, so uncomment these lines.
-  #host: localhost
-  #port: 5432
-
-  # Schema search path. The server defaults to $user,public
-  #schema_search_path: myapp,sharedapp,public
-
-  # Minimum log levels, in increasing order:
-  #   debug5, debug4, debug3, debug2, debug1,
-  #   log, notice, warning, error, fatal, and panic
-  # Defaults to warning.
-  #min_messages: notice
-
-# Warning: The database defined as "test" will be erased and
-# re-generated from your development database when you run "rake".
-# Do not set this db to the same as development or production.
-test:
-  <<: *default
-  database: <%= app_name %>_test
-
-# As with config/credentials.yml, you never want to store sensitive information,
-# like your database password, in your source code. If your source code is
-# ever seen by anyone, they now have access to your database.
-#
-# Instead, provide the password or a full connection URL as an environment
-# variable when you boot the app. For example:
-#
-#   DATABASE_URL="postgres://myuser:mypass@localhost/somedatabase"
-#
-# If the connection URL is provided in the special DATABASE_URL environment
-# variable, Rails will automatically merge its configuration values on top of
-# the values provided in this file. Alternatively, you can specify a connection
-# URL environment variable explicitly:
-#
-#   production:
-#     url: <%%= ENV["MY_APP_DATABASE_URL"] %>
-#
-# Read https://guides.rubyonrails.org/configuring.html#configuring-a-database
-# for a full overview on how database connection configuration can be specified.
-#
-production:
-  <<: *default
-  database: <%= app_name %>_production
-  username: <%= app_name %>
-  password: <%%= ENV["<%= app_name.upcase %>_DATABASE_PASSWORD"] %>

data/lib/rails/generators/rails/app/templates/config/databases/jdbcsqlite3.yml.tt

@@ -1,24 +0,0 @@
-# SQLite. Versions 3.8.0 and up are supported.
-#   gem "activerecord-jdbcsqlite3-adapter"
-#
-# Configure Using Gemfile
-# gem "activerecord-jdbcsqlite3-adapter"
-#
-default: &default
-  adapter: sqlite3
-  pool: <%%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
-
-development:
-  <<: *default
-  database: storage/development.sqlite3
-
-# Warning: The database defined as "test" will be erased and
-# re-generated from your development database when you run "rake".
-# Do not set this db to the same as development or production.
-test:
-  <<: *default
-  database: storage/test.sqlite3
-
-production:
-  <<: *default
-  database: storage/production.sqlite3

data/lib/rails/generators/rails/app/templates/config/databases/oracle.yml.tt

@@ -1,62 +0,0 @@
-# Oracle/OCI 11g or higher recommended
-#
-# Requires Ruby/OCI8:
-#  https://github.com/kubo/ruby-oci8
-#
-# Specify your database using any valid connection syntax, such as a
-# tnsnames.ora service name, or an SQL connect string of the form:
-#
-#   //host:[port][/service name]
-#
-# By default prefetch_rows (OCI_ATTR_PREFETCH_ROWS) is set to 100. And
-# until true bind variables are supported, cursor_sharing is set by default
-# to 'similar'. Both can be changed in the configuration below; the defaults
-# are equivalent to specifying:
-#
-#  prefetch_rows: 100
-#  cursor_sharing: similar
-#
-default: &default
-  adapter: oracle_enhanced
-  pool: <%%= ENV.fetch("RAILS_MAX_THREADS") { 5 } %>
-  username: <%= app_name %>
-  password:
-
-development:
-  <<: *default
-  database: <%= app_name %>_development
-
-# Warning: The database defined as "test" will be erased and
-# re-generated from your development database when you run "rake".
-# Do not set this db to the same as development or production.
-test:
-  <<: *default
-  database: <%= app_name %>_test
-
-# As with config/credentials.yml, you never want to store sensitive information,
-# like your database password, in your source code. If your source code is
-# ever seen by anyone, they now have access to your database.
-#
-# Instead, provide the password or a full connection URL as an environment
-# variable when you boot the app. For example:
-#
-#   DATABASE_URL="oracle-enhanced://myuser:mypass@localhost/somedatabase"
-#
-# (Note that the adapter name uses a dash instead of an underscore.)
-#
-# If the connection URL is provided in the special DATABASE_URL environment
-# variable, Rails will automatically merge its configuration values on top of
-# the values provided in this file. Alternatively, you can specify a connection
-# URL environment variable explicitly:
-#
-#   production:
-#     url: <%%= ENV["MY_APP_DATABASE_URL"] %>
-#
-# Read https://guides.rubyonrails.org/configuring.html#configuring-a-database
-# for a full overview on how database connection configuration can be specified.
-#
-production:
-  <<: *default
-  database: <%= app_name %>_production
-  username: <%= app_name %>
-  password: <%%= ENV["<%= app_name.upcase %>_DATABASE_PASSWORD"] %>

data/lib/rails/generators/rails/app/templates/config/databases/sqlserver.yml.tt

@@ -1,53 +0,0 @@
-# SQL Server (2012 or higher required)
-#
-# Install the adapters and driver
-#   gem install tiny_tds
-#   gem install activerecord-sqlserver-adapter
-#
-# Ensure the activerecord adapter and db driver gems are defined in your Gemfile
-#   gem "tiny_tds"
-#   gem "activerecord-sqlserver-adapter"
-#
-default: &default
-  adapter: sqlserver
-  encoding: utf8
-  username: sa
-  password: <%%= ENV["SA_PASSWORD"] %>
-  host: localhost
-
-development:
-  <<: *default
-  database: <%= app_name %>_development
-
-# Warning: The database defined as "test" will be erased and
-# re-generated from your development database when you run "rake".
-# Do not set this db to the same as development or production.
-test:
-  <<: *default
-  database: <%= app_name %>_test
-
-# As with config/credentials.yml, you never want to store sensitive information,
-# like your database password, in your source code. If your source code is
-# ever seen by anyone, they now have access to your database.
-#
-# Instead, provide the password or a full connection URL as an environment
-# variable when you boot the app. For example:
-#
-#   DATABASE_URL="sqlserver://myuser:mypass@localhost/somedatabase"
-#
-# If the connection URL is provided in the special DATABASE_URL environment
-# variable, Rails will automatically merge its configuration values on top of
-# the values provided in this file. Alternatively, you can specify a connection
-# URL environment variable explicitly:
-#
-#   production:
-#     url: <%%= ENV["MY_APP_DATABASE_URL"] %>
-#
-# Read https://guides.rubyonrails.org/configuring.html#configuring-a-database
-# for a full overview on how database connection configuration can be specified.
-#
-production:
-  <<: *default
-  database: <%= app_name %>_production
-  username: <%= app_name %>
-  password: <%%= ENV["<%= app_name.upcase %>_DATABASE_PASSWORD"] %>