Bearbeiten von „Server/SRS1/2017“

* die [[Plone]]-Kiste
'''Lauffähig'''

== Plone ==

Plone 4.0.5 via UnifiedInstaller installieren.

 <code>
 install.sh --password=<password>  standalone
 </code>

Plone 4.0.5 to 4.1 fehlgeschlagen

* im verzeichnis von …/GenericSetup die rolemap.xml angelegt
link : [https://plone.org/documentation/kb/grant-collection-attopic-permissions-to-contributors-and-editors]

 <?xml version="1.0" encoding="UTF-8"?>
 <rolemap>
  <permissions>
    <permission name="ATContentTypes Topic: Add ATBooleanCriterion" acquire="True">
      <role name="Contributor"/>
    </permission>
    <permission name="ATContentTypes Topic: Add ATCurrentAuthorCriterion" acquire="True">
      <role name="Contributor"/>
    </permission>
    <permission name="ATContentTypes Topic: Add ATDateCriteria" acquire="True">
      <role name="Contributor"/>
    </permission>
    <permission name="ATContentTypes Topic: Add ATDateRangeCriterion" acquire="True">
      <role name="Contributor"/>
    </permission>
    <permission name="ATContentTypes Topic: Add ATListCriterion" acquire="True">
      <role name="Contributor"/>
    </permission>
    <permission name="ATContentTypes Topic: Add ATPathCriterion" acquire="True">
      <role name="Contributor"/>
    </permission>
    <permission name="ATContentTypes Topic: Add ATPortalTypeCriterion" acquire="True">
      <role name="Contributor"/>
    </permission>
    <permission name="ATContentTypes Topic: Add ATReferenceCriterion" acquire="True">
      <role name="Contributor"/>
    </permission>
    <permission name="ATContentTypes Topic: Add ATRelativePathCriterion" acquire="True">
      <role name="Contributor"/>
    </permission>
    <permission name="ATContentTypes Topic: Add ATSelectionCriterion" acquire="True">
      <role name="Contributor"/>
    </permission>
    <permission name="ATContentTypes Topic: Add ATSimpleIntCriterion" acquire="True">
      <role name="Contributor"/>
    </permission>
    <permission name="ATContentTypes Topic: Add ATSimpleStringCriterion" acquire="True">
      <role name="Contributor"/>
    </permission>
    <permission name="ATContentTypes Topic: Add ATSortCriterion" acquire="True">
      <role name="Contributor"/>
    </permission>
    <permission name="Add portal topics" acquire="True">
      <role name="Contributor"/>
    </permission>
    <permission name="Change portal topics" acquire="True">
       <role name="Editor"/>
     </permission>
  </permissions>
 </rolemap>

== [[Server/Jails/SRS1/Ports |Ports]] ==
{{:Server/Jails/SRS1/Ports}}

== Konfiguration der Programme ==

=== Konfiguration Plone ===
; für Backup aktivierung
* in die buildout.cfg schreiben unter der überschrift [buildout]
 ########################################## ##
 # Parts Specification
 #--------------------
 # Specifies the components that should be included in the buildout.
 # All the basics are in the base.cfg extension; you may add your
 # own if you need them at the end of this file.
 parts =
    instance
    zopepy
    zopeskel
    unifiedinstaller
    chown
    '''backup'''
    '''repozo'''

* [backup] am Schluss hin schreiben und weitere Parameter eintragen (buildout.cfg)
 [backup]
 recipe = collective.recipe.backup
 keep = 4
 full = true
 debug = false
 snapshotlocation = /root/plonebackup/snapshot
 backup_blobs = true
 blobsnapshotlocation = /root/plonebackup/blobsnapshots
 gzip = true
 enable_snapshotrestore = false

; wenn die Datei repozo.py fehlte (buildout.cfg)

 [repozo]
 recipe = zc.recipe.egg
 eggs = ZODB3
 scripts = repozo

; /etc/crontab

 # Plone inkrementelles Backup
 *       23      *       *       6       root    <path/to/plone>/zinstance/bin/backup
 # Plone Fullbackup (snapshot)
 *       20      5       *       *       root    <path/to/plone>/zinstance/bin/snapshotbackup

=== Konfiguration Apache22 ===

* httpd.conf

 <code>
 ServerTokens ProductOnly
 ServerSignature Off
 </code>

* extra/httpd-vhost.conf

 <code>
 <VirtualHost *:80>
 
 # A sample VirtualHost section for using Apache as a webserver
 # instead of Zope.
 # ServerName is the url of your website.
 
 ServerName '''<domain>'''
 # ServerName 127.0.0.1
 # Add serverAlias lines for other domain names that should
 # point to this website. They will be rewritten by Apache to
 # the ServerName, so that anyone going to www.site.com
 # will be invisibly redirected to site.com in their browser.
 
 ServerAlias '''domain'''
 
 # ServerAdmin is your email address, which shows up on error
 # pages when Apache cannot connect to Zope.
 
 ServerAdmin '''adminmail'''
 
 # The ProxyPass and ProxyPassReverse lines are the magic
 # ingredients. They rewite requests to http://site.com and
 # pass the entire request through to Zope on
 # http://site.com:8080. The VirtualHostBase ensures that
 # when the page goes back to the browser, it goes out through
 # Apache, and appears to have come from http://site.com.
 
 # The line is made up from:
 
 # ProxyPass or ProxyPassReverse
 
 # / is the url at http://site.com that you wish to use to
 # point to the Zope site. You could keep http://site.com as a
 # flat HTML site in Apache, and replace / with /zope to make
 # http://site/com/zope point to your zope site.
 # http://site.com:8080 is the address that your zope is
 # running on.
 
 # /VirtualHostBase/http/site.com:80 makes sure that zope
 # *thinks* it is running at http://site.com instead of at
 # http://site.com:8080. You don't have to do anything else
 # in Zope to make this work.
 
 # /yourplonesite is the location of your Plone Site within Zope.
 # If you added a Plone Site into the root of your Zope with an id
 # of 'mysite', then you just change this bit to /mysite
 
 # /VirtualHostRoot/ makes your Plone site think it is the root of the site.
 
 ProxyPass / http://127.0.0.1:8080/VirtualHostBase/http/'''<domain>''':80/Plone/VirtualHostRoot/
 ProxyPassReverse / http://127.0.0.1:8080/VirtualHostBase/http/'''<domain>''':80/Plone/VirtualHostRoot/
 
 # CacheRoot is the location on the filesystem to store files that
 # Apache caches. This directory must be created, and the user that
 # Apache runs as must have full write permissions to it.
 # It's a bad idea to create this in the /tmp directory, as the
 # directory itself will then be deleted when you reboot.
 
 CacheRoot "/var/cache/www.stura.htw-dresden.de"
 CacheEnable disk /
 
 # CacheSize determines how big this cache can get in KB. It's a
 # good idea that this number is about 30% less than the available
 # space in the CacheRoot directory. Here we choose to cache 100MB
 # of data, which is enough for a personal website, but not for
 # anything larger.
 MCacheSize 524288
 MCacheMaxObjectCount 100000
 MCacheMinObjectSize 1
 MCacheMaxObjectSize 200000
 # CacheGcInterval specifies how often (in hours) to examine the
 # cache and delete obsolete files.
 #CacheGcInterval 2
 
 # CacheLastModifiedFactor allows the estimation of an expiry date
 # for a page if it doesn't have an expiry-date specified in the
 # HTTP headers returned from Zope. This is based on (time since
 # last modification * CacheLastModifiedFactor), so that content
 # that is ten hours old would be given an expiry date of 1 hour in
 # the future.
 CacheLastModifiedFactor 0.1
 
 # CacheDefaultExpire sets a default expiry time of 0,5 hour into the
 # future for cached pages.
 CacheDefaultExpire 0.5
 
 # CacheDirLength sets the number of characters used in directory
 # names for subdirectories of CacheRoot
 CacheDirLength 3
 
 # The following definitions set expiry times for various content
 # types. In this list, each content type defined is cached for a
 # maximum period of 1 hour (3600 seconds) before it must be checked
 # again. Non-listed content types are not cached.
 
 ExpiresActive On
 expiresByType image/ief A3600
 ExpiresByType image/tiff A3600
 ExpiresByType image/bmp A3600
 ExpiresByType image/gif A3600
 ExpiresByType image/png A3600
 ExpiresByType image/jpeg A3600
 ExpiresByType image/x-cmu-raster A3600
 ExpiresByType image/x-portable-anymap A3600
 ExpiresByType image/x-portable-bitmap A3600
 ExpiresByType image/x-portable-graymap A3600
 ExpiresByType image/x-portable-pixmap A3600
 ExpiresByType image/x-rgb  A3600
 ExpiresByType image/x-xbitmap A3600
 ExpiresByType image/x-xpixmap A3600
 ExpiresByType image/x-xwindowdump A3600
 ExpiresByType text/css A3600
 ExpiresByType text/javascript A3600
 ExpiresByType application/x-javascript A3600
 ExpiresByType text/html A3600
 ExpiresByType text/xml A3600
 
 # CustomLog "/var/log/www.stura.htw-dresden.de-access_log" common
 
 </VirtualHost>
 </code>

== Weblinks ==
* [http://www.imn.htwk-leipzig.de/~mfrank/lehre/osem_10/CBecker_Backup_Datensicherung_Vortrag.pdf PDF File für Plone 4 Backup]
* [https://plone.org/documentation/manual/upgrade-guide Upgrade Manual]

[[Kategorie:Rechentechnik]]
[[Kategorie:Software]]
[[Kategorie:Jail]]
@@ Zeile 1: / Zeile 1: @@
-; Verwendungszweck:
+* die [[Plone]]-Kiste
-* [[Plone]] ([[Website]]) für [http://www.stura.htw-dresden.de www.stura.htw-dresden.de]
+'''Lauffähig'''
-* [[w:de:Webschnittstelle|Webschnittstelle]] [[Chat]] für [http://chat.htw.stura-dresden.de chat.htw.stura-dresden.de]
-'''Lauft!'''
 == Plone ==
@@ Zeile 251: / Zeile 248: @@
   </VirtualHost>
   </code>
-== Konfiguration von Skripten ==
-==== rc.d scripting Plone ====
-Seit Anbeginn (nun mehrere Jahre) hat der Betrieb von [[Plone]] auf [[srs1]] ein großes Manko: Plone startet nicht von allein. Daher musste sich auf [[srs1]] manuell angemeldet werden und [[Plone]] musste "von Hand" gestartet werden. Das soll nun anders sein.
-: <code>$EDITOR /usr/local/etc/rc.d/plone</code>
-<pre>
-#!/bin/sh
-# PROVIDE: plone
-# REQUIRE: LOGIN
-# KEYWORD: shutdown
-. /etc/rc.subr
-name="plone"
-rcvar=plone_enable
-start_cmd="${name}_start"
-stop_cmd="${name}_stop"
-restart_cmd="${name}_restart"
-status_cmd="${name}_status"
-extra_commands="status"
-load_rc_config ${name}
-#: ${plone_enable:="NO"}
-plone_stop()
-{
-        /usr/local/Plone/zinstance/bin/plonectl stop
-}
-plone_status()
-{
-        /usr/local/Plone/zinstance/bin/plonectl status
-}
-plone_start()
-{
-        /usr/local/Plone/zinstance/bin/plonectl start
-}
-plone_restart()
-{
-        /usr/local/Plone/zinstance/bin/plonectl restart
-}
-run_rc_command "$1"
-</pre>
-Anpassen der Berechtigung für eine Datei für ''rc.d''
-: <code>chmod 540 /usr/local/etc/rc.d/plone</code>
-: Kontrollieren der Berechtigung für eine Datei für ''rc.d''
-:: <code>ls -l /usr/local/etc/rc.d/plone</code>
-<pre>
--r-xr-----  1 root  wheel  603 Oct 23 18:34 /usr/local/etc/rc.d/plone
-</pre>
-Selbstverständlich bedarf es auch noch dem Eintrag in der ''rc.conf'', um Anzuzeigen, dass ''plone '' gestartet werden soll kann.
-: <code>echo 'plone_enable="YES"' >> /etc/rc.conf</code>
-Eigentlich ist die Datei für ''rc.d'' relativ simpel. (Der Bezug sind die komplexen Varianten, die ''rc.d'' und entsprechende Dateien mit sich brinken können.)
-* ''/usr/local/Plone/zinstance/bin/plonectl'' ist die Stelle und Datei zur Verwaltung des Betriebes von Plone. (Woher die Auswahl dieses Stelle stammt ist nicht näher bekannt.)
-* Bei der Entfernung der Auskommentierung bei '''''#''': ${plone_enable:="NO"}'' würde Plone nicht zu Starten der Jail selbst starten. Jedoch wären aber noch alle anderen gewünschten Funktionalitäten von ''rc.d'' verfügbar.
-* Folgende Befehle sind nun mittels ''rc.d'' verfügbar:
-** <code>service plone stop</code>
-**: Stoppen von Plone
-** <code>service plone stauts</code>
-**: Status von Plone ausgeben lassen
-** <code>service plone start</code>
-**: Starten von Plone
-** <code>service plone restart</code>
-**: Neustarten von Plone
-*:.
-Läuft!
 == Weblinks ==