|
|
# Background
|
|
|
To run & manage the various application templates (Linux, MySQL, Apache, an email service, and a CMS) that make up a complete civiCRM package on different clouds and virtualization platforms (including , OpenStack, AWS, Rackspace, Microsoft Azure, Google Compute Engine, DigitalOcean, IBM SoftLayer, etc.)
|
|
|
|
|
|
## Coding Week One
|
|
|
## Coding Phase One
|
|
|
### Task
|
|
|
* [ ] Making it easy to provide the absolute system path at runtime from the environment in CiviCRM rather than hardcoded in a file - issue #6 and issue #12
|
|
|
* [ ] Making it easy to provide the absolute system path at runtime from the environment in CiviCRM rather than hardcoded in a file - issue #6 and issue #12
|
|
|
|
|
|
### Milestones
|
|
|
## Coding Phase Two
|
|
|
### Task
|
|
|
* [ ] Identifying and declaring in the config file the directories that should be writable in production - issue #2 and issue #3
|
|
|
|
|
|
## Coding Pase Three
|
|
|
### Task
|
|
|
* [ ] Redesign the configuration system of civiCRm to manage configuration as code and content. That is, allow user configuration from the UI, but safe export of configuration to disk where it can be checked into Git and then safely reimported on deploy - issue #4
|
|
|
* [ ] User Testing
|
|
|
|
|
|
## Weekly Milestones
|
|
|
#### Week One
|
|
|
1. Get proxying working for an application like drupal that allows it and then see how it breaks when the same is tried with civicrm to understand the problem domain
|
|
|
2. Implement `/buildkit/build/dmaster/sites/default/civicrm.settings.php` on lines 236 - 238 to mimic `/buildkit/build/dmaster/sites/default/settings.php` on lines 333 |
|
|
|
|
|
### Estimated Time
|
|
|
7 days
|
|
|
|