You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@allura.apache.org by br...@apache.org on 2013/03/19 20:29:23 UTC

[5/10] git commit: [#5973] symlink pysvn instead of using --system-site-packages

[#5973] symlink pysvn instead of using --system-site-packages


Project: http://git-wip-us.apache.org/repos/asf/incubator-allura/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-allura/commit/ec22e94c
Tree: http://git-wip-us.apache.org/repos/asf/incubator-allura/tree/ec22e94c
Diff: http://git-wip-us.apache.org/repos/asf/incubator-allura/diff/ec22e94c

Branch: refs/heads/db/5973
Commit: ec22e94c394bb576f747f91b658008d1d40c7186
Parents: f309470
Author: Dave Brondsema <db...@geek.net>
Authored: Mon Mar 18 13:37:40 2013 -0700
Committer: Dave Brondsema <db...@geek.net>
Committed: Tue Mar 19 12:26:04 2013 -0700

----------------------------------------------------------------------
 README.markdown |    9 +++++++--
 1 files changed, 7 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-allura/blob/ec22e94c/README.markdown
----------------------------------------------------------------------
diff --git a/README.markdown b/README.markdown
index d380157..248b8a7 100644
--- a/README.markdown
+++ b/README.markdown
@@ -38,7 +38,7 @@ The first step to installing the Allura platform is installing a virtual environ
 
 Once you have virtualenv installed, you need to create a virtual environment.  We'll call our Allura environment 'anvil'.
 
-    ~$ virtualenv --system-site-packages anvil
+    ~$ virtualenv anvil
 
 This gives us a nice, clean environment into which we can install all the allura dependencies.
 (The --system-site-packages flag is to include the python-svn package).  In order to use the virtual environment, you'll need to activate it:
@@ -62,6 +62,10 @@ Although the application setup.py files define a number of dependencies, the `re
 
 This will take a while.  If you get an error from pip, it is typically a temporary download error.  Just run the command again and it will quickly pass through the packages it already downloaded and then continue.
 
+Optional, for SVN support: symlink the system pysvn package into our virtual environment
+
+    (anvil)~/src/allura$ ln -s /usr/lib/python2.7/dist-packages/pysvn ~/anvil/lib/python2.7/site-packages/
+
 And now to setup the Allura applications for development.  If you want to setup all of them, run `./rebuild-all.bash`
 If you only want to use a few tools, run:
 
@@ -85,6 +89,7 @@ We have a custom config ready for use.
     (anvil)~/src$ cd apache-solr-1.4.1/example/
     (anvil)~/src/apache-solr-1.4.1/example/$ mkdir -p ~/src/allura/solr_config/conf
     (anvil)~/src/apache-solr-1.4.1/example/$ cp solr/conf/solrconfig.xml ~/src/allura/solr_config/conf/
+    (anvil)~/src/apache-solr-1.4.1/example/$ mkdir ~/logs/
     (anvil)~/src/apache-solr-1.4.1/example/$ nohup java -Dsolr.solr.home=$(cd;pwd)/src/allura/solr_config -jar start.jar > ~/logs/solr.log &
 
 
@@ -101,7 +106,7 @@ In order to initialize the Allura database, you'll need to run the following:
 
     (anvil)~/src/allura/Allura$ paster setup-app development.ini
 
-This shouldn't take too long, but it will start the taskd server doing tons of stuff in the background.  It should complete in 5-6 minutes.  Once this is done, you can start the application server:
+This shouldn't take too long, but it will start the taskd server doing tons of stuff in the background.  Once this is done, you can start the application server:
 
     (anvil)~/src/allura/Allura$ nohup paster serve --reload development.ini > ~/logs/tg.log &