Changes between Version 409 and Version 410 of TracInstall

Timestamp:

Apr 26, 2015, 12:32:24 AM (9 years ago)

Author:

Ryan J Ollos

Comment:

Partial revert of TracInstall@408. The $ are useful for indicating that the command is executed at a shell prompt.

TracInstall

@@ -122 +122 @@
 
  - Install Trac 1.0:
-   {{{#!sh
-   easy_install Trac==1.0
-   }}}
+ {{{#!sh
+$ easy_install Trac==1.0
+}}}
  - Install latest development version:
-   {{{#!sh
-   easy_install Trac==dev
-   }}}
+ {{{#!sh
+$ easy_install Trac==dev
+}}}
    Note that in this case you won't have the possibility to run a localized version of Trac;
    either use a released version or install from source.
@@ -147 +147 @@
  - 
  {{{#!sh
-pip install trac psycopg2 
+$ pip install trac psycopg2 
 }}}
 or:
  - 
  {{{#!sh
-pip install trac mysql-python 
+$ pip install trac mysql-python 
 }}}
 
@@ -168 +168 @@
 
 {{{#!sh
-python ./setup.py install
+$ python ./setup.py install
 }}}
 
@@ -178 +178 @@
 If you install from source and want to make Trac available in other languages, make sure Babel is installed. Only then, perform the `install` (or simply redo the `install` once again afterwards if you realize Babel was not yet installed):
 {{{#!sh
-python ./setup.py install
+$ python ./setup.py install
 }}}
 
@@ -195 +195 @@
 To install Trac to a custom location, or find out about other advanced installation options, run:
 {{{#!sh
-easy_install --help
+$ easy_install --help
 }}}
 
@@ -202 +202 @@
 Specifically, you might be interested in:
 {{{#!sh
-easy_install --prefix=/path/to/installdir
+$ easy_install --prefix=/path/to/installdir
 }}}
 
 or, if installing Trac on a Mac OS X system:
 {{{#!sh
-easy_install --prefix=/usr/local --install-dir=/Library/Python/2.5/site-packages
+$ easy_install --prefix=/usr/local --install-dir=/Library/Python/2.5/site-packages
 }}}
 
@@ -220 +220 @@
 A new environment is created using [TracAdmin trac-admin]:
 {{{#!sh
-trac-admin /path/to/myproject initenv
+$ trac-admin /path/to/myproject initenv
 }}}
 
@@ -238 +238 @@
 Finally, make sure the user account under which the web front-end runs will have '''write permissions''' to the environment directory and all the files inside. This will be the case if you run `trac-admin ... initenv` as this user. If not, you should set the correct user afterwards. For example on Linux, with the web server running as user `apache` and group `apache`, enter:
 {{{#!sh
-chown -R apache.apache /path/to/myproject
+$ chown -R apache.apache /path/to/myproject
 }}}
 
@@ -253 +253 @@
 After having created a Trac environment, you can easily try the web interface by running the standalone server [TracStandalone tracd]:
 {{{#!sh
-tracd --port 8000 /path/to/myproject
+$ tracd --port 8000 /path/to/myproject
 }}}
 
 Then, fire up a browser and visit `http://localhost:8000/`. You should get a simple listing of all environments that `tracd` knows about. Follow the link to the environment you just created, and you should see Trac in action. If you only plan on managing a single project with Trac you can have the standalone server skip the environment list by starting it like this:
 {{{#!sh
-tracd -s --port 8000 /path/to/myproject
+$ tracd -s --port 8000 /path/to/myproject
 }}}
 
@@ -271 +271 @@
 Alternatively, the variable can be set in the shell before executing `tracd`:
 {{{#!sh
-PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1 tracd --port 8000 /path/to/myproject
+$ PKG_RESOURCES_CACHE_ZIP_MANIFESTS=1 tracd --port 8000 /path/to/myproject
 }}}
 }}}
@@ -291 +291 @@
 There is, however, a bit of a chicken-and-egg problem. The [TracAdmin trac-admin] command requires an existing environment to function, but complains if the deploy directory already exists. This is a problem, because environments are often stored in a subdirectory of the deploy. The solution is to do something like this:
 {{{#!sh
-mkdir -p /usr/share/trac/projects/my-project
-trac-admin /usr/share/trac/projects/my-project initenv
-trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy
-mv /tmp/deploy/* /usr/share/trac
+$ mkdir -p /usr/share/trac/projects/my-project
+$ trac-admin /usr/share/trac/projects/my-project initenv
+$ trac-admin /usr/share/trac/projects/my-project deploy /tmp/deploy
+$ mv /tmp/deploy/* /usr/share/trac
 }}}
 
@@ -319 +319 @@
 Assuming the deployment has been done this way:
 {{{#!sh
-trac-admin /var/trac/env deploy /path/to/shared/trac
+$ trac-admin /var/trac/env deploy /path/to/shared/trac
 }}}
 
@@ -362 +362 @@
 Of course, you still need to make the Trac `htdocs/common` directory available through the web server at the specified URL, for example by copying (or linking) the directory into the document root of the web server:
 {{{#!sh
-ln -s /path/to/trac/htdocs/common /var/www/static.example.org/trac-common
+$ ln -s /path/to/trac/htdocs/common /var/www/static.example.org/trac-common
 }}}
 
@@ -386 +386 @@
 Grant admin rights to user admin:
 {{{#!sh
-trac-admin /path/to/myproject permission add admin TRAC_ADMIN
+$ trac-admin /path/to/myproject permission add admin TRAC_ADMIN
 }}}