Experimental way to customize LAMP stack

software/drupal/software.cfg

@@ -19,3 +19,8 @@ location = ${buildout:parts-directory}/${:_buildout_section_name_}
 
 [application-configuration]
 location = sites/default/default.settings.php
+
+[custom-application-deployment]
+path = {:_profile_base_location_}/instance.cfg
+part-list =
+  setup-database

stack/lamp/apache/instance-apache-php.cfg

 [buildout]
+extends = ${custom-php-part:path}
 
 parts =
   certificate-authority
@@ -14,6 +15,7 @@ parts =
   frontend-promise
   content-promise
   publish-connection-informations
+  ${custom-php-part:part-list}
 
 eggs-directory = ${buildout:eggs-directory}
 develop-eggs-directory = ${buildout:develop-eggs-directory}

stack/lamp/buildout.cfg

@@ -61,6 +61,18 @@ recipe = hexagonit.recipe.download
 #If provided tarball does not containt top directory this option shall be changed to false
 strip-top-level-dir = true
 
+[custom-application-deployment]
+# Optional part allowing applications using this stack to run a custom
+# instance.cfg at the end of Apache/PHP instance deployment.
+# To use it in your application, just override those two parameters, like:
+# path = /path/to/instance-custom.cfg
+# part-list =
+#  part1
+#  part2
+# See software/drupal/software.cfg for an example.
+path =
+part-list =
+
 [template]
 recipe = slapos.recipe.template
 url = ${:_profile_base_location_}/instance.cfg