Skip to content
This repository has been archived by the owner on Mar 27, 2022. It is now read-only.

Commercial Hosting Inquiries

Tim Morgan edited this page Feb 23, 2017 · 10 revisions

I've (Tim) had a few people ask about offering commercial hosted SaaS solutions for OneBody, and to that I say, YES a million times YES!!!

I am super excited that churches without a strong technical person could sign up for your service, click a few buttons, and get their own OneBody site in a few minutes. That makes me happy!

Conditions

So, yes do it! I just ask that you follow these rules:

  1. Honor the license. AGPL in a nutshell means you must open-source any changes you make. Configuration files don't matter, but any code changes should land on your GitHub account, and preferablly make their way back to churchio/onebody as a Pull Request.

  2. Do NOT use the "Church.IO" name in your promotion. You are welcome to use the name "OneBody" however you like, but you are not to use "Church.IO" to sell the product, as it is a trademark of our federation of developers, and I don't want it to be confused with your company.

  3. You must provide your own support. If you don't have an experienced Rails developer on staff and a support person who can field questions from churches, don't bother. And certainly do not send any customer support inquires to me directly.

  4. If a support question results in a found bug, please fix the bug and submit a Pull Request. If you absolutely don't know where to start, then chat me and ask for some advice, but not before you do some digging yourself.

Promotion on https://church.io

I intend to create a page on https://church.io pointing people to hosting options. If your hosting option isn't crappy, then I'll link to it.

If there are more than one commercial option, I will do my best not to choose favorites.

Is OneBody Multitenant?

Yes it is!