Fellowship One & Planning Center Online
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:
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:
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”.
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)
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:
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)
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
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,
- Include Requirements & Contribution Sub Types
- User Case Story from Hope Community Church
- Group Search Categories and More
- Account Creation
- Single Sign On Functionality Exposed
- API Communication Value Changes
- API Enhancement: Create and Edit Groups!
- API Enhancement: Requirements Exposed
- Resource Versioning
- Enter Visitor Data via Your Church Website
- Fellowship One & Planning Center Online
- API Libraries and Sample Code
- Building a custom login for your church website using the API
- Roll Foward!
- The Agile Triangle
- Conversation Paralysis
- Picture this, image updates & creates through the REST API
- A REST API double shot : Groups and Events realms
- Increasing Software Delivery by 500%
- Quick people API realm update
- Introducing the new REST API giving realm
- Raising the bar…
- Building a Deployment Pipeline
- The World of Dev Craft
- Running Tests in Parallel with Selenium
- Abstracting Your Code to Remove Duplication
- Documentation in an Agile Environment
- Drowning in Debt
- Intro to Ruby on Rails
- API Strategy & Roadmap
- Staging/Sandbox Environment is Back up!
- Downtime in Sandbox/Staging Environment
- Android & OAuth
- F1 API Static Library with Objective-c
- Programming in F#
- NoSQL: HuMONGOus Benefits (Part 2)
- Our Scrum Team Structure
- SaaS & BI - The History & Future
- Getting Started with Android
- NoSQL: Leaving Schema Behind (Part 1)
- Your Feedback…and a $25 Gift Card!
- A Scrum Ceremony? Is this a wedding or something?
- Variables in PHP
- Data Exchange API Fixes
- F1 Check-in on the iPad
- Be the first to get the news & tips!
- An Introduction to PHP
- Working with Pop Up Windows in Selenium
- List Comprehension
- Source Control: A Time Machine For Your Source Code
- Developer Conference…Lower Price, Same Great Content!
- The Quality Assurance Team
- How does Fellowship Technologies manage complex projects?
- Developer Conference coming in May!
- Sandbox Refresh Complete
- Sandbox Refresh This Week
- Updates coming to the REST API
- Sandbox Environment Down Time
- F1Touch :: Fellowship One On The Go
- Under the Hood
- Sandbox Refresh Complete
- Sandbox Refresh Tomorrow (Oct. 2nd)
- Fellowship One Developer Forums
- Ten Commandments of API Consumption
- REST API Enhancements / Fixes deployed to Sandbox and Production 09.09.09
- Data Exchange URL cut-over complete
- Important Data Exchange URL changes
- Ron Nom Nom
- How to get started using the REST API