Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
O
osticket
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
Container Registry
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
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
docker
osticket
Commits
ed6c837c
Commit
ed6c837c
authored
13 years ago
by
Jared Hancock
Browse files
Options
Downloads
Plain Diff
Merge branch 'hotfix/readme' into develop
parents
2bdbafec
a65c0406
No related branches found
Branches containing commit
Tags
v1.8.0
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+15
-4
15 additions, 4 deletions
README.md
with
15 additions
and
4 deletions
README.md
+
15
−
4
View file @
ed6c837c
...
@@ -18,10 +18,21 @@ easy to setup and use. The best part is, it's completely free.
...
@@ -18,10 +18,21 @@ easy to setup and use. The best part is, it's completely free.
Installation
Installation
------------
------------
Download the
osTicket now supports bleeding-edge installations. The easiest way to
[
source
](
./zipball/master
)
from
install the software and track updates is to clone the public repository.
the GitHub page. Follow the instructions for installation on the osTicket
Create a folder on you web server (using whatever method makes sense for
[
wiki
](
http://osticket.com/wiki/Installation
)
.
you) and cd into it. Then clone the repository (the folder must be empty!):
git clone https://github.com/osTicket/osTicket-1.7 .
osTicket uses the git flow development model, so you’ll need to switch to
the develop branch in order to see the bleeding-edge feature additions.
git checkout develop
Follow the usual install instructions (beginning from Manual Installation
above), except, don't delete the setup/ folder. For this reason, such an
installation is not recommended for a public-facing support system.
Help
Help
----
----
...
...
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