"Fossies" - the Fresh Open Source Software Archive

Member "Plone-5.2.5-UnifiedInstaller-1.0/buildout_templates/buildout.cfg" (13 Sep 2021, 6152 Bytes) of package /linux/www/Plone-5.2.5-UnifiedInstaller-1.0.tgz:


As a special service "Fossies" has tried to format the requested source page into HTML format using (guessed) INI source code syntax highlighting (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file. See also the latest Fossies "Diffs" side-by-side code changes report for "buildout.cfg": 5.2.4-UnifiedInstaller-1.0_vs_5.2.5-UnifiedInstaller-1.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 # https://docs.plone.org/manage/installing/installing_addons.html
   20 # Full details at http://pypi.python.org/pypi/zc.buildout
   21 #
   22 ############################################
   23 
   24 
   25 [buildout]
   26 
   27 # buildout.sanitycheck makes sure you're not running buildout
   28 # as root.
   29 # extensions =
   30 #     buildout.sanitycheck
   31 
   32 ############################################
   33 # Plone Component Versions
   34 # ------------------------
   35 # This version of the Unified Installer has the components of Plone 5
   36 # preloaded so that it can install without an Internet connection.
   37 # If you want to update, uncomment the "http://..." line below,
   38 # edit it to point to the current version URL, comment out the
   39 # "versions.cfg" line and run "bin/buildout" while attached to the
   40 # Internet. Generally, you only want to do that as part of a planned migration.
   41 # Note that if you are updating components, you should also check the versions
   42 # section at the end of this file, since recipes or components other than
   43 # those of Zope and Plone may need updating at the same time.
   44 #
   45 extends =
   46     base.cfg
   47     https://dist.plone.org/release/5.2.5/versions.cfg
   48 
   49 
   50 # This user will own the non-data parts of the installation, and should be used to
   51 # run buildout.
   52 buildout-user = plone_buildout
   53 # A flag to tell the Unified Installer whether or not to document sudo use.
   54 need-sudo = yes
   55 
   56 
   57 ############################################
   58 # Eggs
   59 # ----
   60 # Add an indented line to the eggs section for any Python
   61 # eggs or packages you wish to include in your Plone instance.
   62 #
   63 # Note that versions may be specified here or in the [versions]
   64 # section below. You should always specify versions that you know
   65 # are compatible with the Plone release and at an acceptable
   66 # development level.
   67 #
   68 # If you update to a later version of Plone, remove the hotfix.
   69 #
   70 eggs =
   71     Plone
   72 
   73 
   74 ############################################
   75 # ZCML Slugs
   76 # ----------
   77 # Some eggs need ZCML slugs to tell Zope to
   78 # use them. This is increasingly rare.
   79 zcml =
   80 #    plone.reload
   81 
   82 
   83 ############################################
   84 # Development Eggs
   85 # ----------------
   86 # You can use paster to create "development eggs" to
   87 # develop new products/themes. Put these in the src/
   88 # directory.
   89 # You will also need to add the egg names in the
   90 # eggs section above, and may also need to add them
   91 # to the zcml section.
   92 #
   93 # Provide the *paths* to the eggs you are developing here:
   94 develop =
   95 #    src/my.package
   96 
   97 
   98 ############################################
   99 # var Directory
  100 # -------------
  101 # Sets the target directory for the "var" components of the install such as
  102 # database and log files.
  103 #
  104 var-dir=${buildout:directory}/var
  105 
  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 ############################################
  118 # Initial User
  119 # ------------
  120 # This is the user id and password that will be used to create the initial
  121 # user id that will allow you to log in and create a Plone site. This only
  122 # sets the initial password; it will not allow you to change an already
  123 # existing password. If you change the admin password via the web interface,
  124 # the one below will no longer be valid.
  125 # If you find yourself locked out of your Zope/Python installation, you may
  126 # add an emergency user via "bin/plonectl adduser".
  127 user=admin:__PASSWORD__
  128 
  129 
  130 ############################################
  131 # Debug Options
  132 # -------------
  133 # Start Zope/Plone instances in "fg" mode to turn on debug mode;
  134 # this will dramatically slow Plone.
  135 #
  136 # Add-on developers should turn deprecation warnings on
  137 deprecation-warnings = off
  138 # change verbose-security to "on" for useful security errors while developing
  139 verbose-security = off
  140 
  141 
  142 ############################################
  143 # Parts Specification
  144 #--------------------
  145 # Specifies the components that should be included in the buildout.
  146 # Most are defined in the base.cfg extension; you may add your
  147 # own if you need them at the end of this file.
  148 parts =
  149     instance
  150     zeoserver
  151     client1
  152     repozo
  153     backup
  154     zopescripts
  155     zopepy
  156     unifiedinstaller
  157     setpermissions
  158     precompiler
  159 
  160 
  161 ############################################
  162 # Major Parts
  163 # ----------------------
  164 # These common parts make use of sane base settings from
  165 # base.cfg. To customize a part, just add whatever options
  166 # you need. Read base.cfg for common settings.
  167 
  168 
  169 [instance]
  170 <= instance_base
  171 recipe = plone.recipe.zope2instance
  172 http-address = 8080
  173 
  174 [zeoserver]
  175 <= zeoserver_base
  176 recipe = plone.recipe.zeoserver
  177 zeo-address = 127.0.0.1:8100
  178 # __ZEO_CLIENTS_HERE__
  179 
  180 ############################################
  181 # Versions Specification
  182 # ----------------------
  183 # Version information supplied here will "pin" Python packages to a particular
  184 # version number, even when you use the "newest" flag running buildout.
  185 # Specifying versions for all packages is a good idea and can prevent
  186 # accidental changes when you add new packages to your buildout.
  187 # Note that versions specified here will override those specified earlier
  188 # in the configuration, including those from the Plone and Zope version
  189 # config files.
  190 #
  191 [versions]
  192 # other pins not in plone
  193 plone.recipe.unifiedinstaller = 5.2b1
  194 buildout.sanitycheck = 1.0.2
  195 collective.recipe.backup = 4.1.0
  196 
  197 # only for Windows
  198 nt-svcutils = 2.13.0