Campaign Monitor Facebook Subscribe Forms

A Facebook canvas application which allows Facebook users to add Campaign Monitor subscribe forms to their Facebook Pages. Named cmfbsub as some sort of mix between an acronym and an abbreviation for Campaign Monitor Facebook Subscribe Forms.

How it works

Campaign Monitor lists the Facebook subscribe form in its list of integrations, where you can find a brief summary of what the app does. The app is available as either a white-labelled version named Subscribe Form, or as a Campaign Monitor branded version named Campaign Monitor Subscribe Form.

The white-labelled version of the app can be accessed at https://apps.facebook.com/createsend/ and the Campaign Monitor branded version can be accessed at https://apps.facebook.com/campaignmonitor/. These apps are implemented as Canvas Pages and run in an iframe within the Facebook chrome.

The Sinatra application in this repository is what runs in the iframe. The same code is deployed to two different Heroku apps for the two different versions of the app. The white-labelled version of the app runs at https://csfbsub.herokuapp.com/ and the Campaign Monitor branded version of the app runs at https://cmfbsub.herokuapp.com/.

Developing

1. Get added as a developer on FB by an existing admin with access to the production and development apps.
2. Get admin privileges for the prod and dev apps in Heroku.

The Unix based OS is recommended for Ruby development, as it makes everything easier to install and configure for this application.
Clone:

git clone https://github.com/campaignmonitor/cmfbsub.git && cd cmfbsub/

Bundle:

bundle install

There are a few config settings required to run the app which are stored in environment variables. When working locally, config settings are read from a .env file (which is obviously entered into .gitignore).

Create a .env file based on .env.example:

cp .env.example .env

Edit .env to include the config settings found on the Local Dev Campaign Monitor Subscribe admin page. You might like to reference the config settings for the development app devcmfbsub on Heroku (you'll need access to the Heroku app):

heroku config --app devcmfbsub

Which will show you something like:

=== devcmfbsub Config Vars
APP_API_KEY:                  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
APP_CANVAS_NAME:              devcampaignmonitor
APP_DOMAIN:                   devcmfbsub.herokuapp.com
APP_ID:                       111111111111111
APP_NAME:                     devcmfbsub
APP_SECRET:                   xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
...

Run the tests:

bundle exec rake

Running the app locally

To run the app locally, install foreman with gem install foreman:

foreman start

That will start the app at http://localhost:5000/, however you will need to set up a secure tunnel so that the app is available to run inside the Facebook iframe over HTTPS.

Download and extract ngrok somewhere. Then run:

./ngrok http 5000

Then you'll see something similar to:

ngrok

Tunnel Status        online
Version              1.7/1.7
Forwarding           http://3a4j20f9.ngrok.com -> 127.0.0.1:5000
Forwarding           https://3a4j20f9.ngrok.com -> 127.0.0.1:5000
Web Interface        127.0.0.1:4040
# Conn               0
Avg Conn Time        0.00ms

Your local app is then accessible over HTTPS at https://3a4j20f9.ngrok.com (the subdomain will be different). The last step is to visit the devcmfbsub Facebook app to modify the required settings and let the Facebook app know where our local application is running.

On the main settings page:

• "Secure Canvas URL" should be: https://3a4j20f9.ngrok.com/
• "Secure Page Tab URL" should be: https://3a4j20f9.ngrok.com/tab/

On the advanced settings page:

• "Deauthorize Callback URL" should be: https://3a4j20f9.ngrok.com/ondeauth

Then visit the ldevcmfbsub Facebook app at http://apps.facebook.com/ldevcampaignmonitor/ for testing locally, which will load https://3a4j20f9.ngrok.com (http://localhost:5000) in the iframe inside the Facebook chrome.

Deploying

To be able to deploy the app, you will need to be a collaborator on each of the Heroku apps where the app is deployed. In addition to the two production versions of the app (https://apps.facebook.com/campaignmonitor/ and https://apps.facebook.com/createsend/), there is also a development version at https://apps.facebook.com/devcampaignmonitor/ which corresponds to the Heroku app at https://devcmfbsub.herokuapp.com/. You should always push and test your changes using the development app before pushing the production versions of the app.

You'll need to set up git remotes to point to each version of the app on Heroku, which you can do like so:

git remote add devcmfbsub git@heroku.com:devcmfbsub.git
git remote add cmfbsub git@heroku.com:cmfbsub.git
git remote add csfbsub git@heroku.com:csfbsub.git

So, you would now push to devcmfbsub to deploy the development version of the app, and push to cmfbsub and csfbsub to deploy both the Campaign Monitor branded and white-label versions of the app.

In the alternative, to deploy directly to Heroku: First, you need to install the Heroku CLI.

To get a list of remotes -

git remote -v

then, for example if you want to connect to dvcmfbsub:

heroku git:remote -a devcmfbsub

you can then push directly to Heroku:

git push heroku master

This stuff should be green