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

Allow a custom Gemfile for local development #9

Closed
aldesantis opened this issue Nov 22, 2019 · 2 comments · Fixed by #72
Closed

Allow a custom Gemfile for local development #9

aldesantis opened this issue Nov 22, 2019 · 2 comments · Fixed by #72
Assignees

Comments

@aldesantis
Copy link
Member

aldesantis commented Nov 22, 2019

Some extension developers may want to use their own tools such as Pry or Byebug to develop and debug extensions. However, these shouldn't be installed automatically for all users, since everyone has their preference.

We could recommend adding the following to an extension's Gemfile:

load 'Gemfile-custom'

By ignoring Gemfile-custom in Git, users will essentially have a way to use their preferred debugging tools in the extension.

Related issues

@aldesantis aldesantis self-assigned this Nov 29, 2019
@elia
Copy link
Member

elia commented Nov 29, 2019

Consider using Gemfile.local which seems to be quite common, or to drop the thing entirely and let maintainers just set BUNDLE_GEMFILE=Gemfile.local, see also rubygems/bundler#183.

@aldesantis
Copy link
Member Author

Gemfile.local sounds good, I think we can just add it to .gitignore and add something like the following to the Gemfile we generated with the template:

load 'Gemfile.local' if File.exists?('Gemfile.local')

@aldesantis aldesantis changed the title Allow a custom Gemfile for local development? Allow a custom Gemfile for local development Jan 3, 2020
@aldesantis aldesantis removed their assignment Jan 3, 2020
@elia elia self-assigned this Jan 17, 2020
@elia elia closed this as completed in #72 Jan 17, 2020
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

Successfully merging a pull request may close this issue.

2 participants