Our #CiviOneClick hybrid sessions during the very well organised sprint in Hamburg were differently as expected: less coding, but therefore lots of important discussions on the architecture of #CiviOneClick in order to make it adaptable for as many user stories and different contexts as possible.

We discussed with Tim and Ben from the Core Team, Michael from Third Sector Design, Ahmet from Skvare and very motivated and persistent community members, about the environment variables of Standalone, fpm and/or apache web server, data portability, data export and backup. We also created a new wording to specify the preconfigured installs provided with CiviOneClick: it’s “flavors” (it’s summer, so we got inspired by ice cream :-). So we thought about ways how to install extensions and flavor extensions and the first flavor (for event organisations) got created.

If you want to contribute to the discussions or to solving some of the issues, please have a look at GitLab. Any contribution is highly appreciated!

Michael from Third Sector has been spending many hours creating an amazing Docker image, which meets the requirements of #CiviOneClick, will become the official Docker image of CiviCRM - maintained by the Core Team - and can also be used by the community in many other contexts.

All in one box (with different layers), the image allows an easier installation with CiviCRM Standalone. Don't we all like to unwrap parcels? :-)

Here you can find the repository of the current image.

Some issues are still pending. If you want to support the coding process, have a look at for example the issue of "flavor" extension, which would allow the user to install a set of extensions and configurations that meet a particular use case, e.g. sports clubs or event organisers.