Skip to content

Instantly share code, notes, and snippets.

@Serg0
Forked from taisyo7333/ruby_on_rails5.md
Created March 12, 2018 16:37
Show Gist options
  • Save Serg0/a5b01d47d882b803b9a5c931b90fb63d to your computer and use it in GitHub Desktop.
Save Serg0/a5b01d47d882b803b9a5c931b90fb63d to your computer and use it in GitHub Desktop.

Revisions

  1. Daisuke Inoue revised this gist Nov 22, 2017. 1 changed file with 2 additions and 0 deletions.
    2 changes: 2 additions & 0 deletions ruby_on_rails5.md
    Original file line number Diff line number Diff line change
    @@ -8,6 +8,8 @@ Run `bundle install` to install missing gems.
    # 解決
    ```
    # bundle install --binstubs
    または
    # rails app:update:bin
    # bundle exec rails g
    ```
  2. Daisuke Inoue created this gist Nov 22, 2017.
    105 changes: 105 additions & 0 deletions ruby_on_rails5.md
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,105 @@
    # 現象
    ```
    # bundle exec rails c
    Could not find rake-12.3.0 in any of the sources
    Run `bundle install` to install missing gems.
    ```

    # 解決
    ```
    # bundle install --binstubs
    # bundle exec rails g
    ```

    # ログ
    ```
    Looks like your app's ./bin/rails is a stub that was generated by Bundler.
    In Rails 5, your app's bin/ directory contains executables that are versioned
    like any other source code, rather than stubs that are generated on demand.
    Here's how to upgrade:
    bundle config --delete bin # Turn off Bundler's stub generator
    rails app:update:bin # Use the new Rails 5 executables
    git add bin # Add bin/ to source control
    You may need to remove bin/ from your .gitignore as well.
    When you install a gem whose executable you want to use in your app,
    generate it and add it to source control:
    bundle binstubs some-gem-name
    git add bin/new-executable
    remove /controllers/test_controller.rb
    invoke erb
    remove /views/test
    invoke test_unit
    remove test/controllers/test_controller_test.rb
    invoke helper
    remove /helpers/test_helper.rb
    invoke test_unit
    invoke assets
    invoke coffee
    invoke scss
    Usage:
    rails new APP_PATH [options]
    Options:
    -r, [--ruby=PATH] # Path to the Ruby binary of your choice
    # Default: /usr/local/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
    [--skip-yarn], [--no-skip-yarn] # Don't use Yarn for managing JavaScript dependencies
    [--skip-gemfile], [--no-skip-gemfile] # Don't create a Gemfile
    -G, [--skip-git], [--no-skip-git] # Skip .gitignore file
    [--skip-keeps], [--no-skip-keeps] # Skip source control .keep files
    -M, [--skip-action-mailer], [--no-skip-action-mailer] # Skip Action Mailer files
    -O, [--skip-active-record], [--no-skip-active-record] # Skip Active Record 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
    [--skip-spring], [--no-skip-spring] # Don't install Spring application preloader
    [--skip-listen], [--no-skip-listen] # Don't generate configuration that depends on the listen gem
    [--skip-coffee], [--no-skip-coffee] # Don't use CoffeeScript
    -J, [--skip-javascript], [--no-skip-javascript] # Skip JavaScript files
    [--skip-turbolinks], [--no-skip-turbolinks] # Skip turbolinks gem
    -T, [--skip-test], [--no-skip-test] # Skip test files
    [--skip-system-test], [--no-skip-system-test] # Skip system test files
    [--dev], [--no-dev] # Setup the application with Gemfile pointing to your Rails checkout
    [--edge], [--no-edge] # Setup the application with Gemfile pointing to Rails repository
    [--rc=RC] # Path to file containing extra configuration options for rails command
    [--no-rc], [--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
    [--webpack=WEBPACK] # Preconfigure for app-like JavaScript with Webpack (options: react/vue/angular)
    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
    Description:
    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.
    Example:
    rails new ~/Code/Ruby/weblog
    This generates a skeletal Rails installation in ~/Code/Ruby/weblog.
    ```