move the cache directory so we manage the perms ourselves

Plone-Conference-Devs · Jun 12, 2011 · cca0f01 · cca0f01
1 parent b591d1b
commit cca0f01
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 4 deletions.
diff --git a/.gitignore b/.gitignore
@@ -10,3 +10,4 @@ develop-eggs
 parts
 eggs
 adminPassword.txt
+buildout-cache
diff --git a/live.cfg b/live.cfg
@@ -13,8 +13,8 @@ parts +=
 #    chown-zeo
 
 
-eggs-directory=/data/ploneconf/buildout-cache/eggs
-download-cache=/data/ploneconf/buildout-cache/downloads
+eggs-directory=/data/ploneconf/ploneconfbuildout/buildout-cache/eggs
+download-cache=/data/ploneconf/ploneconfbuildout/buildout-cache/downloads
 
 newest = false
 
@@ -32,7 +32,7 @@ find-links =
 # unzip all eggs for easier debugging
 unzip = true
 
-extends-cache = /data/ploneconf/buildout-cache/downloads/extends
+extends-cache = /data/ploneconf/ploneconfbuildout/buildout-cache/downloads/extends
 
 zeo-address = 127.0.0.1:8100
 # Zope client 1
@@ -49,7 +49,7 @@ verbose-security = off
 # If you try to start Zope as root, it will change user id to run as
 # the effective user specified here. This user id must own the var directory
 # of your buildout.
-effective-user = ploneconf
+effective-user = plone
 
 
 [zopepy]