[buildout] extends = # buildout.hash.cfg is used for automated hash calculation of managed # instance files by calling update-hash buildout.hash.cfg # "slapos" stack describes basic things needed for 99.9% of SlapOS Software # Releases ../../stack/slapos.cfg ../../stack/monitor/buildout.cfg # Extend here component profiles, like openssl, apache, mariadb, curl... # Or/and extend a stack (lamp, tomcat) that does most of the work for you # In this example we extend from helloweb component. # ../../component/component1/buildout.cfg # ../../component/component2/buildout.cfg ../../component/helloweb/buildout.cfg parts = # Call installation of slapos.cookbook egg defined in stack/slapos.cfg (needed # in 99,9% of Slapos Software Releases) slapos-cookbook # Call creation of instance.cfg file that will be called for deployment of # instance instance-profile # build helloweb programs helloweb-python helloweb-ruby helloweb-go # Macro for jinja templates. The filename is set in buildout.hash.cfg # in the section using this template [jinja-template] recipe = slapos.recipe.template:jinja2 template = ${:_profile_base_location_}/${:filename} mode = 0644 # Download instance.cfg.in (buildout profile used to deployment of instance), # replace all ${foo:bar} parameters by real values, and change $${foo:bar} to # ${foo:bar} # The recipe, template and mode are fetched from jijna-template [instance-profile] # The <= is buildout verb to use defined template <= jinja-template rendered = ${buildout:directory}/instance.cfg extensions = jinja2.ext.do context = section buildout buildout raw template_monitor ${monitor2-template:rendered} # md5sum is fetched from buildout.hash.cfg and can be recalculated automatically by # calling update-hash # Pin versions of eggs used that are not already pinned by stack/slapos.cfg [versions] slapos.recipe.template = 4.4