-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Added 'mini_portile2' #2995
Added 'mini_portile2' #2995
Conversation
Added `gem 'mini_portile2'` because it is needed for `nokogiri`. Tested on NixOS by using `bundle install` and `bundix` to generate `gemset.nix` and build Beef on Nix. This change prevents error by nokogiri.
Thank you @D3vil0p3r. What was the error on NixOS? |
During the building of
To solve this is needed not only to add
So, the user must manually edit the
and in this manner it works. I don't know if it is possible to edit the Gemfile in order to make mini_portile2 to be/to appear in Gemfile.lock as a dependency of nokogiri. |
Thank you. I have it on my list. You can also join our discord server to discuss https://discord.gg/ugmKmHarKc |
Stale pull request message |
Up: not stale |
Thank you @D3vil0p3r. Do you know a different method to using the mini_portile2 gem? It seems to have a lot of runtime functionality? I don't want to increase the attack surface. |
The only idea I have currently is to remove the usage of nokogiri (so miniportal is not needed anymore) and replace it with another dep if needed. Also because in general nokogiri seems to create only issues. |
This is going to be a bigger change. Can you join discord so we can discuss https://discord.gg/ugmKmHarKc |
Already there |
Added
gem 'mini_portile2'
because it is needed fornokogiri
. Tested on NixOS by usingbundle install
andbundix
to generategemset.nix
and build Beef on Nix. This change prevents error by nokogiri.Pull Request
Thanks for submitting a PR! Please fill in this template where appropriate:
Category
e.g. Bug, Module, Extension, Core Functionality, Documentation, Tests
Feature/Issue Description
Q: Please give a brief summary of your feature/fix
A:
Q: Give a technical rundown of what you have changed (if applicable)
A:
Test Cases
Q: Describe your test cases, what you have covered and if there are any use cases that still need addressing.
A:
Wiki Page
If you are adding a new feature that is not easily understood without context, please draft a section to be added to the Wiki below.