#Ami 2016.09 libjansson how to
#Ami 2016.09 libjansson install
#Ami 2016.09 libjansson code
#Ami 2016.09 libjansson download

Now we can proceed with installing missing electron dependencies and compiling from source certain libraries.

#Ami 2016.09 libjansson download

So as the next step we can download the tool into the home directory: curl -o- > ~/eltool.sh & chmod +x ~/eltool.sh The tool is called eltool.sh and is available as gist However instead of simply rewriting a newer version of the article I have decided to put all of the commands and improvements into a script, so that the process can be automated. By now it is a bit outdated and only helps tackle 11 dependencies and misses few important in 2017 parts, but has definitely has saved me a day or two and showed the right approach (and right versions of the libraries to build from source).

#Ami 2016.09 libjansson how to

About a year ago Yuanyi wrote great article on How to run electron on Amazon Linux. We can see that there's total of 14 static libraries missing.

Let's check $ cd dist]$ ldd electron | grep 'not found' It is logical to assume that in case one library is missing, there will be more. node_modules/nightmare/node_modules/electron/dist/electronĮlectron: error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directoryīingo! The dependency error was the first informative error and told us that electron can't run because of missing static library libgtk (which is installed by default on most of Desktop Ubuntu distros, but isn't always available on server distros, on CentOS or on Amazon Linux or Lambda). So let's try to run the electron executable manually: nightmare-test]$. But still we don't know what is the root cause of the problem. Now we get output like below, from which we can conclude that there's problem with running electron executable. Nightmare electron child process not started yet, skipping kill.

#Ami 2016.09 libjansson code

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

#Ami 2016.09 libjansson install

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. You may have thought of running nightmare on AWS Lambda.