I unable to fix this issue when I am deploying my code on Local Remote Environment. Following is my Gemfile
source 'https://rubygems.org' gem 'jets', git: 'https://github.com/tongueroo/jets.git', submodules: true, branch: 'master' # Include pg gem if you are using ActiveRecord, remove next line # and config/database.yml file if you are not gem 'pg', '~> 1.1.3' # A library for generating fake data such as names, addresses, and phone numbers. gem 'faker' gem 'fast_jsonapi' gem 'kaminari' gem 'profanity_filter' gem 'bcrypt' gem 'jwt' gem 'faraday' gem 'oj' # development and test groups are not bundled as part of the deployment group :development, :test do # Call 'byebug' anywhere in the code to stop execution and get a debugger console gem 'byebug', platforms: [:mri, :mingw, :x64_mingw] gem 'puma' gem 'rack' gem 'rubocop', require: false gem 'shotgun' end group :test do gem 'capybara' gem 'database_cleaner-active_record' gem 'factory_bot_rails' gem 'launchy' gem 'rspec' # rspec test group only or we get the "irb: warn: can't alias context from irb_context warning" when starting jets console gem 'shoulda-matchers' gem 'webmock' end
When I’m running
JETS_ENV_REMOTE=1 jets deploy, I get following error:
Checking projects gems for binary Lambda gems... Your project requires compiled gems were not available in any of your lambdagems sources. Unavailable pre-compiled gems: * byebug-11.1.3 * puma-4.3.5 Your current lambdagems sources: * https://gems2.lambdagems.com Jets is unable to build a deployment package that will work on AWS Lambda without the required pre-compiled gems. To remedy this, you can: * Use another gem that does not require compilation. * Create your own custom layer with the gem: http://rubyonjets.com/docs/extras/custom-lambda-layers/ * No need to report this to us, as we've already been notified. Compiled gems usually take some time to figure out how to build as they each depend on different libraries and packages.
I was able to successfully deploy my code before. Now ever since I add couple of gems and use Nokogiri, I think only then this issue is coming up for me.