Mercurial > kallithea

comparison docs/setup.rst @ 2284:e285aa097a81 beta

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
new setup-rhodecode command with optional defaults
author Marcin Kuzminski <marcin@python-works.com>
date Wed, 16 May 2012 23:16:04 +0200
parents 926f55b038bc
children 533a126dc9ab 69df04ee1e2b
comparison
equal deleted inserted replaced
2281:1927dcb05178 2284:e285aa097a81
24 default ensure you properly adjust the db url in your production.ini 24 default ensure you properly adjust the db url in your production.ini
25 configuration file to use this other database. RhodeCode currently supports 25 configuration file to use this other database. RhodeCode currently supports
26 postgresql, sqlite and mysql databases. Create the database by running 26 postgresql, sqlite and mysql databases. Create the database by running
27 the following command:: 27 the following command::
28 28
29 paster setup-app production.ini 29 paster setup-rhodecode production.ini
30 30
31 This will prompt you for a "root" path. This "root" path is the location where 31 This will prompt you for a "root" path. This "root" path is the location where
32 RhodeCode will store all of its repositories on the current machine. After 32 RhodeCode will store all of its repositories on the current machine. After
33 entering this "root" path ``setup-app`` will also prompt you for a username 33 entering this "root" path ``setup-rhodecode`` will also prompt you for a username
34 and password for the initial admin account which ``setup-app`` sets up for you. 34 and password for the initial admin account which ``setup-rhodecode`` sets
35 35 up for you.
36 - The ``setup-app`` command will create all of the needed tables and an admin 36
37 account. When choosing a root path you can either use a new empty location, 37 - The ``setup-rhodecode`` command will create all of the needed tables and an
38 or a location which already contains existing repositories. If you choose a 38 admin account. When choosing a root path you can either use a new empty
39 location which contains existing repositories RhodeCode will simply add all 39 location, or a location which already contains existing repositories. If you
40 of the repositories at the chosen location to it's database. (Note: make 40 choose a location which contains existing repositories RhodeCode will simply
41 sure you specify the correct path to the root). 41 add all of the repositories at the chosen location to it's database.
42 (Note: make sure you specify the correct path to the root).
42 - Note: the given path for mercurial_ repositories **must** be write accessible 43 - Note: the given path for mercurial_ repositories **must** be write accessible
43 for the application. It's very important since the RhodeCode web interface 44 for the application. It's very important since the RhodeCode web interface
44 will work without write access, but when trying to do a push it will 45 will work without write access, but when trying to do a push it will
45 eventually fail with permission denied errors unless it has write access. 46 eventually fail with permission denied errors unless it has write access.
46 47
49 paster serve production.ini 50 paster serve production.ini
50 51
51 - This command runs the RhodeCode server. The web app should be available at the 52 - This command runs the RhodeCode server. The web app should be available at the
52 127.0.0.1:5000. This ip and port is configurable via the production.ini 53 127.0.0.1:5000. This ip and port is configurable via the production.ini
53 file created in previous step 54 file created in previous step
54 - Use the admin account you created above when running ``setup-app`` to login 55 - Use the admin account you created above when running ``setup-rhodecode``
55 to the web app. 56 to login to the web app.
56 - The default permissions on each repository is read, and the owner is admin. 57 - The default permissions on each repository is read, and the owner is admin.
57 Remember to update these if needed. 58 Remember to update these if needed.
58 - In the admin panel you can toggle ldap, anonymous, permissions settings. As 59 - In the admin panel you can toggle ldap, anonymous, permissions settings. As
59 well as edit more advanced options on users and repositories 60 well as edit more advanced options on users and repositories
60 61