![]() ![]() Nightmare electron child process not started yet, skipping kill. Nightmare electron child process exited with code 127: command not found - you may not have electron installed correctly +19ms Nightmare queueing action "evaluate" +0ms Nightmare queueing action "goto" for +3ms ![]() $ DEBUG=nightmare node node_modules/nightmare/example.js # Nightmare will return without any output on the console. ![]() So let's try running example.js: $ node node_modules/nightmare/example.js Npm install nightmare # This will automatically install electron executable as dependency Now let's install nightmare and try running sample mkdir nightmare-test & cd nightmare-test (Note that we will use node 4.3.2 because that's what Lambda Environment docs say. Now let's prepare instance and install some basic tools we need to try to run nightmare. Run "sudo yum update" to apply all updates.Īmazon Linux version 2016.09 is available. Now let's connect to the instance via ssh -i ~/.ssh/my-amazon-linux-keypair.pem _|_ )Ģ2 package(s) needed for security, out of 80 available So now you can launch the Amazon Linux AMI in your preferred way, I would launch Amazon Linux Image via AWS CLI If in your region you find more than one image with this name, you need to pick one with with description "Amazon Linux AMI 2016.03.3 x86_64 HVM GP2". Keep in mind that AMI-image-id for this instance would be different in different regions (eg):īut you can find the right one in your "Community AMIs" section of "EC2 Launch Instance wizard". Provision instance which replicates Lambda environmentĪccording to AWS Documentation on Lambda Execution Environment and available Libraries we would need this AMI image with this alias amzn-ami-hvm-2016.03.3.x86_64-gp2. But before we can run it on Lambda, we need first to make it run on Amazon Linux. Handle=10.SERV/CROSSREF index=200 Į may have thought of running nightmare on AWS Lambda. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |