Facebook Photo Analyzer
- Goto https://developer.facebook.com
- Sign in and click hover over My Apps at the top, then click new app.
- Click Website for the app type
- Click Skip and Create App ID
- Give your application a name and category. Click "Create App ID".
- Leave the page open on Facebook that it brings you to. It should have an App ID and App Secret displayed at the top. We will need this info later.
Quick and easy
Click the following button
You might get a screen asking you to create an alias on DevOps services. If you do just use the part before the @ sign in your email address. Example if your email is email@example.com your username would be johnsmith*
Once the deployment is done, skip to step 10 below.
Create a Bluemix Account
Sign up for Bluemix, or use an existing account.
Download and install the Cloud-foundry CLI tool
Download and install Git
Clone the app to your local environment from your terminal using the following command
git clone https://github.com/IBM-Bluemix/facebook-photo-analyzer.git
- cd into this newly created directory
manifest.ymlfile and change the
<application-host>to something unique.
applications: - name: facebook-photo-analyzer framework: node runtime: node12 memory: 256M instances: 1 host: facebook-photo-analyzer path: . command: node app.js
The host you use will determinate your application url initially, e.g.
Connect to Bluemix in the command line tool and follow the prompts to log in.
$ cf api https://api.ng.bluemix.net $ cf login
If you want to deploy this app to the EU region in London use the following
$ cf api https://api.eu-gb.bluemix.net $ cf login
If you want to deploy this app to the Asia/Pacific region in Australia use the following
$ cf api https://api.au-syd.bluemix.net $ cf login
Create the Visual Recognition service in Bluemix.
$ cf create-service visual_recognition free visual-recognition-photo-analyzer
- Create the Cloudant service in Bluemix.
$ cf create-service cloudantNoSQLDB Shared cloudant-photo-analyzer
- Push it to Bluemix. We need to perform additional steps once it is deployed, so we will add the option --no-start argument
$ cf push --no-start
- In the Bluemix UI click on your application. At the top of the screen there will be a url for your application, ex.
http://facebook-photo-analyzer.mybluemix.net. Copy this and go back to your Facebook app tab in your browser. We need to use this url as our application URL.
- Click "Settings" on the left hand side and then click "Add Platform"
- Click WWW
- Type in the URL for your application, ex.
http://myapp.mybluemix.net, click "Save Changes".
- On the left click Dashboard, copy the Facebook app ID.
- Go back to Bluemix and click on Environment variables on the left hand side.
- Click on user defined
- For the name of the enviroment variable enter
FACEBOOK_APP_ID. For the value paste your Facebook app ID.
- Go back to Facebook, copy the app secret. Go back to Bluemix. Repeat step 4 expect this time the variable name is
FACEBOOK_APP_SECRET. Paste in the value for the Facebook app secret.
- When we signed up for the Alchemy API we should of recieved an API key in our email. We need to create an environment variable to store this. Create another environment variable called
ALCHEMY_API_KEY, paste in api key for Alchemy for the value.
- Click save.
- Click overview in the top left.
- On the right hand side, click restart or start.
The Personality Box sample web application includes code to track deployments to Bluemix and other Cloud Foundry platforms. The following information is sent to a [Deployment Tracker] [deploy_track_url] service on each deployment:
- Application Name (
- Space ID (
- Application Version (
- Application URIs (
This data is collected from the
VCAP_APPLICATION environment variable in IBM Bluemix and other Cloud Foundry platforms. This data is used by IBM to track metrics around deployments of sample applications to IBM Bluemix. Only deployments of sample applications that include code to ping the Deployment Tracker service will be tracked.
Disabling Deployment Tracking
Deployment tracking can be disabled by removing
require("cf-deployment-tracker-client").track(); from the beginning of the
app.js main server file.