You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it is going to install a bunch of things. But maybe we should not do this and instead, like how Paperclip does it. If you want to use S3 storage, and the user tries to run it, then prompt something like this:
Could not load s3 gem. Install and require it in your environment.
Instead of adding a bunch of dependencies to the gem as shown above.
For example if you could care less about CloudFiles or Pony for Email nofications, then why install it?
Install it manually or add it to gemfile if you are using Rails when needed, notify the user with a prompt when trying to load in something that doesn't exist.
Who here likes the approach? Cause maybe when working with bundler for example, it might become a dependency hell for anyone that has gems that depend on different versions of the gem above.
The text was updated successfully, but these errors were encountered:
So for example, looking at our gemspec file:
it is going to install a bunch of things. But maybe we should not do this and instead, like how Paperclip does it. If you want to use S3 storage, and the user tries to run it, then prompt something like this:
Instead of adding a bunch of dependencies to the gem as shown above.
For example if you could care less about CloudFiles or Pony for Email nofications, then why install it?
Install it manually or add it to gemfile if you are using Rails when needed, notify the user with a prompt when trying to load in something that doesn't exist.
Who here likes the approach? Cause maybe when working with bundler for example, it might become a dependency hell for anyone that has gems that depend on different versions of the gem above.
The text was updated successfully, but these errors were encountered: