Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
R
rt
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
best-practical
rt
Commits
3ddc46da
Commit
3ddc46da
authored
14 years ago
by
Kevin Falcone
Browse files
Options
Downloads
Patches
Plain Diff
a few minor cleanups to README, it wants more
(cherry picked from commit
514c9e1b
)
parent
ac8a1700
Branches
7.x-1.x
Tags
7.x-1.3
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README
+6
-16
6 additions, 16 deletions
README
with
6 additions
and
16 deletions
README
+
6
−
16
View file @
3ddc46da
...
...
@@ -50,11 +50,6 @@ o Various and sundry perl modules
GENERAL INSTALLATION
--------------------
This is a rough guide to installing RT. For more detail, you'll
want to read a more comprehensive installation guide at:
http://wiki.bestpractical.com/index.cgi?InstallationGuides
1 Unpack this distribution other than where you want to install RT
To do this cleanly, run the following command:
...
...
@@ -72,10 +67,11 @@ want to read a more comprehensive installation guide at:
default install directory in /opt/rt4 does not work under SELinux's
default configuration.
If you're upgrading RT
then it is worth reading
the UPGRADING document at
If you're upgrading RT
plrease review
the UPGRADING document at
this point. Some extensions you are using may have been integrated into the
core. Use a new, clean directory when you're upgrading to a new major
release (for example from 3.6.x to 3.8.x).
core or there may be extra upgrade scripts to run. Use a new, clean
directory when you're upgrading to a new major release (for example
from 3.6.x to 3.8.x or to 4.0.x).
3 Make sure that RT has everything it needs to run.
...
...
@@ -99,7 +95,7 @@ want to read a more comprehensive installation guide at:
It might sometimes be necessary to run "make fixdeps" several times
to install all necessary perl modules.
6 If this is a new installation:
6 If this is a new installation
(not an upgrade)
:
As a user with permission to install RT in your chosen directory, type:
...
...
@@ -168,9 +164,7 @@ want to read a more comprehensive installation guide at:
8 If you're upgrading from RT 2.0:
Use the RT::Extension::RT2toRT3 module to upgrade to the current RT
release. You can download it from CPAN here:
http://search.cpan.org/dist/RT-Extension-RT2toRT3/
Read more in UPGRADING and docs/UPGRADING-2.x
9 Configure the web server, as described in docs/web_deployment.pod, and
the email gateway, as described below.
...
...
@@ -204,10 +198,6 @@ want to read a more comprehensive installation guide at:
optional step.
SETTING UP THE MAIL GATEWAY
---------------------------
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment