Fellowship One & Planning Center Online

Posted By: Tracy Mazelin

How to Fork, Host, Deploy and Contribute to this open source project

It is now possible to sync your Fellowship One people demographic data to your Planning Center Online Account via an open source application that utilizes both the Fellowship One API and the Planning Center Online API.  This blog post is going to walk you through the process of setting up and hosting this application.

What you will need:

  An account on github (free)
  An account on a fully hosted .NET platform as a service such as AppHarbor (free)
  Microsoft SQL Server Management Studio (free)
  Consumer Key and Secret from F1 (apply here)
  Consumer Key and Secret from Planning Center (apply here)

Step 1: Fork the Repo and make a local clone
In order to contribute to another developers project or use their project as a starting point for your own, you will need to fork the repo.  This is done by simply clicking fork on this page https://github.com/fellowshiptech/f1-pco:

img

Once you have done this, you will need to clone a copy of the code to your local machine.  Instructions for doing this can be found here: http://help.github.com/fork-a-repo/

Step 2: Setup your application in AppHarbor

Since this is an ASP.NET MVC application, you will need the appropriate server environment in which to deploy the application.  AppHarbor is a fully hosted .NET Platform as a Service solution, which allows you to deploy any standard .NET application.  They offer a free account with ample resources for a project like this.  Sign up here: https://appharbor.com/

Once you have created your account, you will need to create a new application:

img

Step 3: Install the Free SQL Server Add-on

Installing an MS SQL Server is necessary to run this application.  AppHarbor offers a free add-on for a shared SQL Server instance.  Select the “Yocto” version and click “Install”.

img

Step 4: Use MS SQL Management Studio to connect to Database

Once you have installed the SQL server, AppHarbor will assign a user id and password to access it.  This can be found by clicking the Go to “SQL Server” link found on your SQL Server page in AppHarbor.  You will need the following information:

  Connection String (save for step 6)
  Host
  Username
  Password

Now you will need to open up SQL Management Studio and enter these credentials here, using the “Host” string as the “Server Name” and entering the Login and Password information:

img

Step 5: Run Database Script

Upon successful connection to the SQL server, you will need to run the database script provided in the repo: Scripts/DBScript.sql.  Select File -> Open -> Locate Script -> Execute.

Step 6: Edit web.config

Open up the web.config file and enter the following information:

  Connection String (from step 4)
  F1Consumer Key
  F1Consumer Secret
  PCO Consumer Key
  PCO Consumer Secret

Step 7: Deploy Application to AppHarbor

The last thing you need to do is push the local repository to your AppHarbor Repository URL.  Doing so will trigger the build on AppHarbor.  You will need to get the AppHarbor Repository URL.  Add the remote repository like this:

git remote add appharbor MY_REPOSITORY_URL

Deploy using:

git push appharbor master

That’s it!  Your integration between the two applications is now complete.  By offering this open source code, our hope is that you will contribute back to this project by adding features and functionality.  It is important to note that this is currently setup for one-way syncing only.  The direction is Fellowship One to PCO.  Developing multi-directional syncing capabilities would be a great way to enhance this project!  Also, the application has multi-tenant functionality built in.  If you use this as a single solution for your church, you may want to remove the multi-tenant functionality (requesting church code etc.) and set it up as a 2nd party application.

We hope you find this useful and look forward to hearing about the awesome ways you build upon this framework for enhancing integration between Fellowship One and Planning Center Online!

Posted In: API,

Comments:
Jeff Cox said: on October 15, 2012 at 08:49 PM

Tracy,

How is this project going?  Have there been any bugs?  What contacts does this sync?  Every name in the f1 database?  Or just certain groups or people lists.  I would like more information how this works. 

Thanks.

-Jeff

Tracy Mazelin said: on October 18, 2012 at 02:29 PM

Hi Jeff, I sent you an email so we can connect.

Thanks,
Tracy

Brian Hey said: on October 23, 2012 at 06:33 PM

I setup the app from the staging environment to a test account on Planning center online.  I didn’t get any errors
But I don’t see any changes to the Planning center online contacts.

What data is pushed from F1 to PCO?
What is “People demographic data”?


Thanks Any Help would be greatly appreciated.

Tracy Mazelin said: on October 29, 2012 at 08:24 AM

Hi Brian, take a look at the readme listed here: https://github.com/fellowshiptech/f1-pco - it outlines what is synced ... “name, address and communication values from F1 are synced to PCO”.

Carr Denn said: on December 11, 2013 at 09:00 PM

Hello is this plugin still supported? I have a few questions about testing it.

Tracy Mazelin said: on December 12, 2013 at 10:34 AM

It isn’t supported, no.  It is open source though so if you can get it to work, you are welcome to use it.

Now You Comment

Remember my personal information.   |   Notify me of follow-up comments.

Categories:

Previous Posts:


Subscribe to the RSS feed!