The server does not start with rails s.
The following is the screen that entered "rails s" in the terminal and accessed localhost: 3000.

The terminal for running rails s is here.

rails s
  rails new APP_PATH [options]

 [--no-skip-namespace] # Skip namespace (affects only isolated applications)
  -r, [--ruby = PATH] # Path to the Ruby binary of your choice
                                                             # Default: /Users/masahiro/.rbenv/versions/2.6.3/bin/ruby
  -m, [--template = TEMPLATE] # Path to some application template (can be a filesystem path or URL)
  -d, [--database = DATABASE] # Preconfigure for selected database (options: mysql/postgresql/sqlite3/oracle/frontbase/ibm_db/sqlserver/jdbcmysql/jdbcsqlite3/jdbcpostgresql/jdbc)
                                                             # Default: sqlite3

 [--no-skip-gemfile] # Don't create a Gemfile
  -G, [--skip-git],

 [--no-skip-git] # Skip .gitignore file

 [--no-skip-keeps] # Skip source control .keep files
  -M, [--skip-action-mailer],

 [--no-skip-action-mailer] # Skip Action Mailer files

 [--no-skip-action-mailbox] # Skip Action Mailbox gem

 [--no-skip-action-text] # Skip Action Text gem
  -O, [--skip-active-record],

 [--no-skip-active-record] # Skip Active Record files

 [--no-skip-active-storage] # Skip Active Storage files-P, [--skip-puma],

 [--no-skip-puma] # Skip Puma related files
  -C, [--skip-action-cable],

 [--no-skip-action-cable] # Skip Action Cable files
  -S, [--skip-sprockets],

 [--no-skip-sprockets] # ​​Skip Sprockets files

 [--no-skip-spring] # Don't install Spring application preloader

 [--no-skip-listen] # Don't generate configuration that depends on the listen gem
  -J, [--skip-javascript],

 [--no-skip-javascript] # Skip JavaScript files

 [--no-skip-turbolinks] # Skip turbolinks gem
  -T, [--skip-test],

 [--no-skip-test] # Skip test files

 [--no-skip-system-test] # Skip system test files

 [--no-skip-bootsnap] # Skip bootsnap gem

 [--no-dev] # Setup the application with Gemfile pointing to your Rails checkout

 [--no-edge] # Setup the application with Gemfile pointing to Rails repository
      [--rc = RC] # Path to file containing extra configuration options for rails command

 [--no-no-rc] # Skip loading of extra configuration options from .railsrc file
      [--api],[--no-api] # Preconfigure smaller stack for API only apps
  -B, [--skip-bundle],

 [--no-skip-bundle] # Don't run bundle install
  --webpacker, [--webpack = WEBPACK] # Preconfigure Webpack with a particular framework (options: react, vue, angular, elm, stimulus)

 [--no-skip-webpack-install] # Don't run Webpack install
Runtime options:
  -f, [--force] # Overwrite files that already exist
  -p, [--pretend],

 [--no-pretend] # Run but do not make any changes
  -q, [--quiet],

 [--no-quiet] # Suppress status output
  -s, [--skip],

 [--no-skip] # Skip files that already exist
Rails options:
  -h, [--help],

 [--no-help] # Show this help message and quit
  -v, [--version],

 [--no-version] # Show Rails version number and quit
    The 'rails new' command creates a new Rails application with a default
    directory structure and configuration at the path you specify.
    You can specify extra command-line arguments to be used every time
    'rails new' runs in the .railsrc configuration file in your home directory.
    Note that the arguments specified in the .railsrc file don't affect the
    defaults values ​​shown above in this help message.
    rails new ~/Code/Ruby/weblog
    This generates a skeletal Rails installation in ~/Code/Ruby/weblog.

Although it was still a beginner and launched as Progate
I have been stuck in this state for a few days.

I should try a lot, but keep it in place, avoiding changing directions.
I hope you can teach me the solution.