Skip to content

Open source fork of kOOL - Online church organization tool

License

Notifications You must be signed in to change notification settings

daniel-lerch/openkool

Folders and files

NameName
Last commit message
Last commit date

Latest commit

c1490f0 · Jul 28, 2020

History

42 Commits
May 12, 2020
Jun 29, 2019
Jul 27, 2020
Mar 14, 2020
Jul 27, 2020
Jul 27, 2020
Jul 25, 2020
Mar 14, 2020
Jul 28, 2020
Jul 27, 2020
Jul 25, 2020
Jul 27, 2020
Mar 14, 2020
Mar 14, 2020
Jul 27, 2020
Jul 27, 2020
Jul 25, 2020
Jul 27, 2020
Jul 25, 2020
Jul 25, 2020
Jul 27, 2020
Mar 14, 2020
Jul 27, 2020
Mar 14, 2020
Jul 27, 2020
Mar 14, 2020
Jul 25, 2020
Mar 14, 2020
Jul 27, 2020
Jul 27, 2020
May 8, 2020
Jul 27, 2020
Jul 27, 2020
Jul 26, 2020
May 8, 2020
Jul 28, 2020
Jul 25, 2020
Jul 26, 2020
Jul 25, 2020
Mar 14, 2020
Mar 14, 2020
Mar 14, 2020
Jun 29, 2019
Jun 29, 2019
Jul 27, 2020
Mar 14, 2020
Jul 25, 2020
Mar 14, 2020
Jul 25, 2020
Jul 25, 2020
Mar 14, 2020
Jul 25, 2020

Repository files navigation

OpenKool

This application is a dockerized version of kOOL form churchtool.org.

kOOL is the most advanced open source church organization software which is currently available. Unfortunately, kOOL is built on old software and never had a good architecture. Improving this, however, would result in thousands of merge conflicts for every new upstream version. That is why OpenKool just aims to keep kOOL operational for next the years until there are better alternatives available.

Installation

The recommended deployment option for OpenKool is to use Docker containers. An official image is available at daniellerch/openkool:r47.

For a detailed installation guide please refer to the docs folder.

Upgrading

All major upgrades have to be performed manually as they usually ship with breaking changes which require special attention. Read the changelogs at OpenKool's releases page carefully.

You cannot skip major upgrades. If you want to upgrade from R45 to R48 for example you have to migrate to R46, R47 and finally to R48.

Contributing

Contributions are very welcome. Please open an issue to discuss your wishes before implementing them.