Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
cloud-native
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards
  • Development
  • cloud-native
  • Wiki
  • Home

Last edited by Michael McAndrew Mar 02, 2018
Page history

Home

Cloud Native CiviCRM

Let's get CiviCRM cloud-ready, or at least make a map to doing so!

Why

It is hard to install and run CiviCRM on a PAAS such as Pantheon, Platform.sh, Acquia Cloud, Amazee.io, WPEngine. These cloud services expect applications to be able to handle a dynamic environment whereas CiviCRM expects that it is on a traditional webhost.

This working group is inspired by these articles:

  • https://12factor.net
  • https://platform.sh/blog/6-things-to-do-to-make-your-application-cloud-friendly

Also, see this list of Cloud Providers on the radar.

Get involved

Let's make a list of issues over in the issue queue of this project. These should be used for discussion, while CiviCRM's regular issue queue(s) should be used for actual work.

So we might end up with issues like #1 to discuss the fact that WPEngine doesn't allow CiviCRM to write to templates_c without special config, and we'd use issues over in JIRA (etc) to work on addressing these.

How can I help?

  • Make an issue for your favourite cloud hosting provider, try CiviCRM on it, report back your results.
  • Make an issue for something that doesn't work, talk about how we can improve that.
  • Anything you like!
Clone repository
  • Cloud Providers
  • Home
  • tiotsop gsoc plan