Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bin/dev file collision, could it be prevented ? #146

Closed
bdavidxyz opened this issue Jan 10, 2024 · 2 comments
Closed

bin/dev file collision, could it be prevented ? #146

bdavidxyz opened this issue Jan 10, 2024 · 2 comments

Comments

@bdavidxyz
Copy link

Use case : create a new rails application

rails -v
7.1.2
rails new theapp --force --database=postgresql -j=esbuild -c=tailwind --skip-docker

Will result, despite the "force" option, into an interrupt :

       rails  css:install:tailwind
       apply  /home/david/.rbenv/versions/3.2.2/lib/ruby/gems/3.2.0/gems/cssbundling-rails-1.3.3/lib/install/install.rb
(...)
      append    Procfile.dev
  Add bin/dev to start foreman
    conflict    bin/dev
  Overwrite /home/david/workspace/railsback/flow/theapp/bin/dev? (enter "h" for help) [Ynaqdhm] a

Not a big deal for a simple "rails new" command, but still annoying in many scenario when you have to generate rails skeleton (template) apps, interrupting the build flow.

@bdavidxyz
Copy link
Author

One possible hack is

echo "Y" | rails new theapp --force --database=postgresql -j=esbuild -c=tailwind --skip-docker

See https://stackoverflow.com/a/14397049/2595513

@dhh
Copy link
Member

dhh commented Jan 21, 2024

Fixed in Supported in 1.4.0.

@dhh dhh closed this as completed Jan 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants