# HG changeset patch
# User Marcin Kuzminski <marcin@python-works.com>
# Date 1290090997 -3600
# Node ID 066af351c6d8c9bf7b74230c17b844d6d54aae42
# Parent  e002951ba66d2694282da73aad3f40d5df3f53af
Fixed archivals by passing baseui to scm get method for hg.
Docs update

diff -r e002951ba66d -r 066af351c6d8 docs/setup.rst
--- a/docs/setup.rst	Thu Nov 18 03:39:01 2010 +0100
+++ b/docs/setup.rst	Thu Nov 18 15:36:37 2010 +0100
@@ -12,7 +12,7 @@
  paster make-config RhodeCode production.ini
 
 - This will create `production.ini` config inside the directory
-  this config contains various settings for rhodecode, e.g proxy port, 
+  this config contains various settings for RhodeCode, e.g proxy port, 
   email settings,static files, cache and logging.
 
 ::
@@ -33,7 +33,7 @@
  
  paster serve production.ini
  
-- This command runs the rhodecode server the app should be available at the 
+- This command runs the RhodeCode server the app should be available at the 
   127.0.0.1:5000. This ip and port is configurable via the production.ini 
   file  created in previous step
 - Use admin account you created to login.
@@ -117,14 +117,14 @@
 support anonymous search/user lookups.
 
 If all data are entered correctly, and `ldap-python` is properly installed
-Users should be granted to access rhodecode wit theire ldap accounts. When 
-logging at the first time an special ldap account is created inside rhodecode, 
+Users should be granted to access RhodeCode wit theire ldap accounts. When 
+logging at the first time an special ldap account is created inside RhodeCode, 
 so You can control over permissions even on ldap users. If such user exists 
-already in rhodecode database ldap user with the same username would be not 
-able to access rhodecode.
+already in RhodeCode database ldap user with the same username would be not 
+able to access RhodeCode.
 
 If You have problems with ldap access and believe You entered correct 
-information check out the rhodecode logs,any error messages sent from 
+information check out the RhodeCode logs,any error messages sent from 
 ldap will be saved there.
 
 
@@ -215,7 +215,7 @@
 - long lasting push timeouts ?
 
  - make sure You set a longer timeouts in Your proxy/fcgi settings, timeouts
-   are caused by https server and not rhodecode
+   are caused by https server and not RhodeCode
 
 - large pushes timeouts ?
  
diff -r e002951ba66d -r 066af351c6d8 rhodecode/model/scm.py
--- a/rhodecode/model/scm.py	Thu Nov 18 03:39:01 2010 +0100
+++ b/rhodecode/model/scm.py	Thu Nov 18 15:36:37 2010 +0100
@@ -155,7 +155,8 @@
 
             #TODO: get the baseui from somewhere for this
             if alias == 'hg':
-                repo = backend(repo_path, create=False, baseui=None)
+                from pylons import app_globals as g
+                repo = backend(repo_path, create=False, baseui=g.baseui)
                 #skip hidden web repository
                 if repo._get_hidden():
                     return