kallithea Changeset - 066af351c6d8

Changeset - 066af351c6d8

Parent rev.

Child rev.

[Not reviewed]

beta

0 2 0

Marcin Kuzminski - 15 years ago 2010-11-18 15:36:37
marcin@python-works.com

Fixed archivals by passing baseui to scm get method for hg.
Docs update

2 files changed with 10 insertions and 9 deletions:

docs/setup.rst

rhodecode/model/scm.py

0 comments (0 inline, 0 general)

docs/setup.rst

➞

Show inline comments

@@ @@ -9,13 +9,13 @@ Setting up the application @@
 ::
  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.
 ::
  paster setup-app production.ini
@@ @@ -30,13 +30,13 @@ Setting up the application @@
 - Run
 ::
  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
 .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.
 - Default permissions on each repository is read, and owner is admin. So
   remember to update these if needed.
@@ @@ -114,20 +114,20 @@ Here's a typical ldap setup:: @@
 `Account` and `Password` are optional, and used for two-phase ldap
 authentication so those are credentials to access Your ldap, if it doesn't
 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.
 Nginx virtual host example
 --------------------------
@@ @@ -212,13 +212,13 @@ Troubleshooting @@
  - don't worry RhodeCode works without them too. No extra setup required
 - 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 ?
  - make sure You set a proper max_body_size for the http server

rhodecode/model/scm.py

➞

Show inline comments

@@ @@ -152,13 +152,14 @@ class ScmModel(object): @@
             log.debug('Creating instance of %s repository', alias)
             backend = get_backend(alias)
             #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
             else:
                 repo = backend(repo_path, create=False)

0 comments (0 inline, 0 general)