Advertisement
prakharjoshi

buildout.cfg

Feb 28th, 2016
61
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.52 KB | None | 0 0
  1. ############################################
  2. #
  3. # Buildout Configuration File for Plone
  4. # -------------------------------------
  5. #
  6. # ALWAYS back up all Plone/Zope data and components
  7. # before changing configuration.
  8. #
  9. # Running "bin/buildout" will update your installation,
  10. # installing missing components as necessary.
  11. #
  12. # This will update the add-on products you've added in the eggs= lines.
  13. # This will not, however, upgrade Plone itself (or anything else you've
  14. # pinned with a version specification). To upgrade Plone itself, see the
  15. # comments in "Plone Component Versions".
  16. #
  17. # Tutorial instructions for using zc.buildout for
  18. # configuration management are available at:
  19. # http://plone.org/documentation/tutorial/buildout
  20. # Full details at http://pypi.python.org/pypi/zc.buildout
  21. #
  22. ############################################
  23.  
  24. [buildout]
  25. ############################################
  26. # Plone Component Versions
  27. # ------------------------
  28. # This version of the Unified Installer has the components of Plone 5
  29. # preloaded so that it can install without an Internet connection.
  30. # If you want to update, uncomment the "http://..." line below,
  31. # edit it to point to the current version URL, comment out the
  32. # "versions.cfg" line and run "bin/buildout" while attached to the
  33. # Internet. Generally, you only want to do that as part of a planned migration.
  34. # Note that if you are updating components, you should also check the versions
  35. # section at the end of this file, since recipes or components other than
  36. # those of Zope and Plone may need updating at the same time.
  37. #
  38. extends =
  39. base.cfg
  40. versions.cfg
  41. # http://dist.plone.org/release/5.0/versions.cfg
  42.  
  43. # If you change your Plone version, you'll also need to update
  44. # the repository link below.
  45. find-links +=
  46. http://dist.plone.org/release/5.0
  47.  
  48. # If you try to start Zope as root, it will change user id to run as
  49. # the effective user specified here. This user id must own the var directory
  50. # of your buildout.
  51. effective-user = prakhar
  52. # This user will own the rest of the installation, and should be used to
  53. # run buildout.
  54. buildout-user = prakhar
  55. # A flag to tell the Unified Installer whether or not to document sudo use.
  56. need-sudo = no
  57.  
  58. ############################################
  59. # Eggs
  60. # ----
  61. # Add an indented line to the eggs section for any Python
  62. # eggs or packages you wish to include in your Plone instance.
  63. #
  64. # Note that versions may be specified here or in the [versions]
  65. # section below. You should always specify versions that you know
  66. # are compatible with the Plone release and at an acceptable
  67. # development level.
  68. #
  69. # If you update to a later version of Plone, remove the hotfix.
  70. #
  71. eggs =
  72. Plone
  73. Pillow
  74. collective.easyform
  75.  
  76. ############################################
  77. # ZCML Slugs
  78. # ----------
  79. # Some eggs need ZCML slugs to tell Zope to
  80. # use them. This is increasingly rare.
  81. zcml =
  82. # plone.reload
  83.  
  84. ############################################
  85. # Development Eggs
  86. # ----------------
  87. # You can use paster to create "development eggs" to
  88. # develop new products/themes. Put these in the src/
  89. # directory.
  90. # You will also need to add the egg names in the
  91. # eggs section above, and may also need to add them
  92. # to the zcml section.
  93. #
  94. # Provide the *paths* to the eggs you are developing here:
  95. develop =
  96. src/collective.easyform
  97. # src/my.package
  98.  
  99. ############################################
  100. # var Directory
  101. # -------------
  102. # Sets the target directory for the "var" components of the install such as
  103. # database and log files.
  104. #
  105. var-dir=${buildout:directory}/var
  106.  
  107. ############################################
  108. # Backup Directory
  109. # ----------------
  110. # Sets the target directory for the bin/backup and bin/snapshotbackup
  111. # commands. Default is inside this project's var directory, but ideally
  112. # this should be on a separate volume or backup server.
  113. #
  114. backups-dir=${buildout:var-dir}
  115.  
  116. ############################################
  117. # Initial User
  118. # ------------
  119. # This is the user id and password that will be used to create the initial
  120. # user id that will allow you to log in and create a Plone site. This only
  121. # sets the initial password; it will not allow you to change an already
  122. # existing password. If you change the admin password via the web interface,
  123. # the one below will no longer be valid.
  124. # If you find yourself locked out of your Zope/Python installation, you may
  125. # add an emergency user via "bin/plonectl adduser".
  126. user=admin:EezaQ2ZWMAXe
  127.  
  128. ############################################
  129. # Debug Options
  130. # -------------
  131. # Start Zope/Plone instances in "fg" mode to turn on debug mode;
  132. # this will dramatically slow Plone.
  133. #
  134. # Add-on developers should turn deprecation warnings on
  135. deprecation-warnings = off
  136. # change verbose-security to "on" for useful security errors while developing
  137. verbose-security = off
  138.  
  139. ############################################
  140. # Parts Specification
  141. #--------------------
  142. # Specifies the components that should be included in the buildout.
  143. # Most are defined in the base.cfg extension; you may add your
  144. # own if you need them at the end of this file.
  145. parts =
  146. instance
  147. repozo
  148. backup
  149. zopepy
  150. unifiedinstaller
  151.  
  152. ############################################
  153. # Major Parts
  154. # ----------------------
  155. # These common parts make use of sane base settings from
  156. # base.cfg. To customize a part, just add whatever options
  157. # you need. Read base.cfg for common settings.
  158.  
  159. [instance]
  160. <= instance_base
  161. recipe = plone.recipe.zope2instance
  162. http-address = 8080
  163.  
  164.  
  165. ############################################
  166. # Versions Specification
  167. # ----------------------
  168. # Version information supplied here will "pin" Python packages to a particular
  169. # version number, even when you use the "newest" flag running buildout.
  170. # Specifying versions for all packages is a good idea and can prevent
  171. # accidental changes when you add new packages to your buildout.
  172. # Note that versions specified here will override those specified earlier
  173. # in the configuration, including those from the Plone and Zope version
  174. # config files.
  175. #
  176. [versions]
  177. # Use whatever setuptools and zc.buildout versions that are
  178. # available in our Python environment.
  179. setuptools =
  180. zc.buildout =
  181.  
  182. Pillow = 2.9.0
  183. python-gettext = 1.2
  184.  
  185. MarkupSafe = 0.23
  186. Products.DocFinderTab = 1.0.5
  187. bobtemplates.plone = 1.0b1
  188. buildout.sanitycheck = 1.0.2
  189. collective.checkdocs = 0.2
  190. collective.recipe.backup = 2.20
  191. mr.bob = 0.1.2
  192. plone.recipe.unifiedinstaller = 4.3.2
  193. zest.pocompile = 1.4
  194. zest.releaser = 5.6
  195. colorama = 0.3.3
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement